Auth and multi-tenancy
Org-scoped access, roles, and licensing come for free instead of being built from scratch.
Bring your tool to QuoxYou built the feature.
You built the feature.
Quox is the surround.
Keep your logic. Keep your brand. Hand off the six things every serious tool eventually needs and none of them wants to build twice: auth and multi-tenancy, durable persistence, human approval gates, agent chat, verifiable evidence, and a distribution route.
QuoxCORE is self-hosted. It runs from Docker Compose on hardware you own, so a tool converted onto it ships to your customer’s own machines, not through a vendor cloud in between. Your plugin is a signed bundle installed into that instance.
In plain words
What it is, where it lives, when to reach for it
- What is it
- A guide to moving a tool you already built inside QuoxCORE instead of running it standalone.
- Where do I use it
- In your own codebase, and on the self-hosted QuoxCORE install you or your customer runs.
- When would I use it
- When your tool needs auth, durable storage, approval gates or an audit trail you have not built.
- How do I use it
- Read the archetype nearest your tool, then email [email protected]: residency is invite-only, not a self-serve form.
QuoxCORE is the free, self-hosted platform underneath this. What is QuoxCORE
The surround
Six things you stop building yourself
Durable persistence
Server-side storage that survives a browser clear, not localStorage pretending to be a database.
Human approval gates
Risky actions wait for a real human decision, enforced by the platform, not requested of the model.
Agent chat
Your tool gets a conversational front end for free: ask it questions, hand it tasks, get cited answers.
Verifiable evidence
Every action your tool takes is hash-chained and exportable, not just logged to a file nobody reads.
A distribution route
Your plugin installs into any QuoxCORE the same way ours do. The public marketplace is not open yet.
Conversion examples
What Quox adds, by archetype
Seven shapes of tool we see most. If yours is not here, the surround still applies.
01
MCP server
Quox turns your MCP server into a governed agent tool with approval gates and an audit trail per call.
02
Monitoring dashboard
Quox adds multi-tenant auth, alert routing to agent chat, and durable history instead of a single-tab view.
03
Chat-ops bot
Quox adds human approval gates on destructive commands and a witnessed record of who approved what.
04
Vertical AI agent
Quox adds org isolation, DEFCON-style autonomy limits, and evidence for every decision it makes.
05
Trading or automation bot
Quox adds a human gate before execution, risk caps, a kill switch, and a hash-chained order trail.
06
DevOps runbooks
Quox adds approval-gated execution, fleet-wide reach through QuoxAgent, and a receipt for every run.
07
Report or scraper micro-SaaS
Quox adds durable multi-tenant storage, scheduled runs, and one install path into any QuoxCORE.
The work
What converting actually involves
Four steps, in the order you would do them. Nothing here is on a roadmap.
01
Scaffold
The scaffolder (npx @quoxai/create-quox-plugin) offers eight templates. You get a manifest, a React view and, in the enterprise-extension template, a backend skeleton for a plugin backend. For an MCP server, --from-mcp scaffolds a specialist-agent plugin from its tool list.
02
Move your logic in
Your existing UI becomes the plugin’s view. Server-side logic can move into a plugin backend on managed Quox instances, under the signing and isolation rules in the developer docs. Self-hosted installs from the public release do not run plugin backends yet. Frontends are React today; other frameworks are not supported yet.
03
Declare what you need
The manifest lists the permissions your plugin wants, and the installer shows that list to the administrator before they accept. The sandbox refuses any call your manifest did not declare. Read what each one opens
04
Hand it over
You build and sign a bundle and an administrator installs it on their instance with quox plugin install. Until the marketplace opens, distribution is a direct agreement between you and your customer, not a storefront.
The EU AI Act clock is already running
Article 50 transparency obligations land in August 2026: disclosure that people are interacting with AI, and a record they can point to. A tool converted onto Quox inherits that disclosure and evidence story instead of building it under deadline pressure.
Read how AEE and WARD carry thisHonest status
- The marketplace is coming. It is not open for public listings yet.
- The Plugin SDK is on npm (four packages under the @quoxai scope, version 0.4.1) and public on GitHub under the Apache 2.0 licence. The protocol SDK packages (aee-sdk, ward, volt, aocl) are not on npm yet. No date is set.
- Plugin frontends are React today. Other frameworks are not supported yet.
Early Developer Residency
Invite-only. First year commission-free once the marketplace opens. We work with a small number of converting developers directly, before this is a self-serve form.