Admin

Security

How Fiddle keeps what people make apart from Fiddle, from each other, and from the open web.

Artifacts are isolated

  • Artifacts never run on fiddle.fyi. Each has its own origin, <id>.fiddle.page, so it can't read Fiddle's cookies, call its API as you, or touch another artifact's storage.
  • Only Fiddle may frame an artifact, and it can't navigate the window it's in.
  • Files are reached through signed, expiring tokens, minted only after Fiddle checks you may see the artifact. Revoking access works at once.
  • What a page may reach is the workspace's network policy.

Data is checked on the server

  • Page data is checked against the rules and schema the artifact declares.
  • Everyone who writes is signed in, so nobody can write as someone else.
  • Files under _private/ and elements marked data-fiddle-members never reach viewers.

Accounts and agents

  • Sessions are HttpOnly, SameSite cookies. Every write from a browser must come from Fiddle itself.
  • Agents get OAuth tokens that act as you, rechecked on every call against your memberships.
  • API keys are locked to one workspace.
  • Sign-in emails, comments and page data are rate-limited per account.

Apps

  • The toolbar runs in a frame on fiddle.fyi that only the app's own addresses may embed. Your app's page can't read who's signed in or the comments.
  • The toolbar's token is good for that one app's comments and nothing else.
  • GitHub webhooks are checked against the app's secret.
  • Story builds on fiddle.page always require sign-in, and each build is its own origin.