sites · cookiejar.lol
Records, files and hosting for the sites agents build. One backend, one key per person, one token per site, nothing to provision.
Moved 2026-09-22: this service now lives at cookiejar.lol. Every site answers at <site>.cookiejar.lol; the old sites.fictionfactory.ai names keep working. Keys, site ids and the API url are unchanged. Agents: the notice on /agent/ tells you what to do.
If you are an agent reading this
Your human sent you here. Go to /agent/ and follow it: it tells you what to ask them, where the key is, and how to get set up. Do not start building yet.
This is a closed alpha. There is no signup. Roark hands out keys as a small file; the agent reads it, installs one skill, and from then on provisions a site for every project it builds.
Agent instructions → Portal (sign in with your key) →What a site gets
| Records | A JSON table API. Any JSON up to 350 KB per record, grouped in collections, listed by prefix with paging. No schema, no migrations. |
|---|---|
| Files | Public files at a stable CDN url, private files behind one-hour links, uploads straight from the browser. |
| Hosting | sites is the host. Hand it the source; it builds it and serves it, Next.js with server code or a static build alike, at <site>.cookiejar.lol. Certificates are issued and renewed for you. |
| Your domain | Any hostname you own, on a static or a Next.js site alike. When the domain is registered with us the DNS is written for you in one call; otherwise you get the exact records to create. Every site also reports when it last changed and which build is live, so an agent can tell at a glance. |
| Keys | You hold one key; it makes sites and does everything on the sites it made, nothing on anyone else's. A deployed site gets its own token for its own data. Anything leaked is rotated in one call; data stays. |
How it's built
Plain AWS, wired once: an HTTP API in front of one function, one on-demand table for every site, S3 behind CloudFront for files, and a single multi-tenant CloudFront distribution for hosting. There is no idle cost; a site that gets no traffic costs nothing.
Alpha means
It works, it is tested against the live build, and it will change. Records and files are stable. Hosting is new: static and Next.js server sites both deploy from source today; there is no image optimizer and no ISR yet. The contract in the README is the truth on any given day.