The small things you would otherwise host yourself.
Functions, a document store and hosted sites, inside the same account and the same permissions as everything else.
- TypeScript functions
- Document store
- Hosted sites
-
Functions with declared reach
Write TypeScript, publish it, call it. What a function may touch is declared as a binding and enforced by the runtime, so reading a collection is a capability rather than a connection string.
-
Endpoints without a server
A published function can answer a URL of its own, with its OpenAPI description and a browsable page, open to the world or behind a token.
-
A document store that bills honestly
Projects, collections and JSON documents, priced per operation rather than per instance. Production projects are guarded, and backups are yours to schedule.
-
Sites, with a coding agent
Describe the page, let the agent build it, publish to development, staging or production, each on its own address.
What stays inside the fence
- Customer code runs in an isolated sandbox with its network cut
- Secrets stay in the vault; code receives a capability instead
- Every execution is metered and recorded
- A production project cannot be dropped without typing its key
What your team gets
Five parts, one account, one set of permissions.
-
Chat and Fusion
Ask across models, grounded in your own documents, with citations you can open.
-
Agents
Automations that do the work, ask before anything irreversible, and leave a trail.
-
Knowledge
Your documents, searchable by meaning, with access granted per base and per group.
-
API
An OpenAI compatible endpoint with a budget per key and a receipt per call.
Replace one script nobody wants to own
The one on somebody's laptop that runs every Monday morning.