Everything you touch sits on one runtime
Not a chat box in front of a model. An enterprise stack built from the database up — one governed runtime, and an open catalog around it.
An open catalog outside. Your rules at the door.
We publish into one marketplace, so do verified vendors, and so can you. What crosses into your organisation is your decision — and everyone working inside it inherits that without being asked to think about it.
Marketplace
work.studio · Vendors · Your company
Connectors · Workflows · Agents · Knowledge
One runtime
one login · one audit trail
Isolated per tenant
Credentials never handed out
Every run audited
Cloud, on-prem or local
Built like infrastructure
Anyone can put a chat box in front of a model. The work is everything that has to be true before a company lets that model touch a real system.
- 37
- backend services
- independently deployable
- 20
- shared modules
- isolation, auth and audit, written once
- 506
- schema migrations
- every change versioned and replayable
- 200+
- connectors
- maintained, not scraped from a directory
Isolation is in the database
Tenants are separated by Postgres row-level security, underneath the application — so a forgotten filter returns nothing rather than someone else’s data.
We never hand out your credentials
Secrets stay in a vault scoped to one connection. Automations get permission to use them, never the values themselves.
Every run is on the record
Runs, model calls and token spend land in a warehouse as they happen. "Who did what, at what cost" is a query.
No model lock-in
Route to Claude, GPT, or a model running inside your own network — per agent, per task, changed without rewriting anything.
One control plane. Your data plane.
What is allowed to run is decided in one place. Where it actually runs is your decision — and it can be somewhere we cannot reach.
Control plane · work.studio
Data plane
Shared
Our cloud
Both planes run in our infrastructure, with every tenant separated in the database. Nothing to deploy, nothing to operate.
Best for: Most teams, and every evaluation
Data plane
Your own data plane
Your VPC
An agent inside your network executes the work and dials out to us — so there is no inbound firewall rule, and your credentials and system traffic never leave your VPC.
Best for: Regulated data, private systems
Data plane
On-premise
Your infrastructure
The entire platform, licensed and self-hosted. Both planes are yours, including the models if you want them to be.
Best for: Air-gapped and sovereignty requirements
Everyone builds. Everyone installs.
We are not the only ones who can extend this. Vendors publish for their own products and you publish for your own systems — into one catalog that all three of us then build on.
work.studio
We publish and maintain the core catalog — the connectors, agents and templates every tenant starts from, kept working as the APIs underneath them change.
Visible to every tenant
Software vendors
Verified third parties publish for their own product, maintained by the people who actually own that API — and reach every tenant on the platform without building a distribution channel.
Verified, then visible to every tenant
Your company
You publish for your own systems — the internal API nobody else has, the agent that knows your process. Yours by default, shared outward only if you decide to.
Private to your tenant, enforced in the database
One marketplace
- Publisher identity and verification
- Versioned, with a rollback path
- Visibility scoped per tenant
- Installs recorded like any other run
Into every tenant — including the three above. The connector a vendor maintains is the one you install; the workflow you built is one fewer thing the next team has to. Everyone here is on both ends of this.
One sets the rules. The other works inside them.
Not tiers you buy and not a choice you make once. Your permissions, connections and history follow you across both — and across every way of reaching them.
Building software rather than running it? Work Studio takes a described capability through architecture, code, tests and docs, on the same runtime.
And four ways to reach them
Mobile
Ask and approve by thumb or by voice, with push for anything waiting on you.
Have your architect read the boring parts
The isolation model, the credential handling and the deployment options, in the detail a security review actually asks for.