Site in one command
create-oneorigin-app writes the ONEORIGIN landing build, wrangler config and deploy scripts.
ONEORIGIN
The framework and the agent runtime,
ready in under a minute
Skip the setup. Scaffold a site, call the agent SDK, and run the server side on Base44 backend functions with keys you control.
> npx create-oneorigin-app@latest my-site
Give your project a job
One scaffold. Everything already wired.
Agent SDK
@one.origin/sandbox streams agent turns from your Worker. The key never reaches the browser.
Server side on Base44
Entities, backend functions and API keys run on Base44. No servers to patch.
Keyed API
Bearer keys are hashed with SHA-256 before they touch the database, and revocable per project.
Global edge
Static assets and API routes deploy to Cloudflare Workers, so every region answers from cache.
Docs that match the code
Seven guides at docs.1origin.dev, generated from the same source as this page.
The stack
Batteries in, gotchas out
No servers
No Docker, no SSH, no config files. Workers for the edge, Base44 for state.
Always on
Functions answer every request, and Base44 automations keep running while you sleep.
Takes real action
ooApi creates and lists records for real. Not a mock endpoint.
Remembers
Entities keep your data: items, keys, owners, timestamps, plus the history Base44 stores.
Lives where you are
Wire the same backend to LINE, WhatsApp, Telegram or the browser.
Secure by default
Hashed keys, CORS allow-list, and per-entity access rules.
Server side
Two endpoints, live right now
Both are deployed and answering. Keys are issued per project, and every write is recorded with an owner and a timestamp.
Open in Base44 →GET
/functions/ooHealth200GET
/functions/ooApi?resource=items200POST
/functions/ooApi?resource=items201Missing or wrong key returns 401. Missing title returns 400 title_required.
Same platform. New superpower.
Start from the Base44 template, keep the ONEORIGIN design, ship on your own domain.
Start deploy →FAQ
What do I need installed?
Node 20 or newer. The CLI pulls the template, then wrangler deploys it. No other tooling.
Where does the server side run?
On Base44 backend functions, with entities for storage. The site itself runs on Cloudflare Workers.
How are API keys handled?
You issue a key per project. Only its SHA-256 hash is stored, so the plaintext is shown once.
Can I keep my own domain?
Yes. Point a subdomain at the worker and add a route. Every site here uses that pattern.