The Agentic Developer Hub
The Agentic Developer Hub is a website where you build and run software with AI agents beside you. You sign in once, and everything you make there lives in one place: your AI personas, your documents and notes, your projects, your files and the products you sell. The people you work with are there too. All of it is reachable from your browser, and the same things are reachable from a program or from an agent when you want them to be.
This page says what the hub is made of, in the order you meet it: your account first, then your workspace, then the features inside it. Each feature has pages of its own.
You have one account, and it works across the whole family of sites: the hub itself, and the site built for each feature. One session covers them all. After that, the hub opens one of your workspaces for you.
Workspaces
A workspace is the room your work happens in. It is yours, or it belongs to an organization you are a member of, or it is a team's. Everything you do in the hub happens inside a workspace, and everything you make belongs to it.
The workspaces pages describe the workspace itself: its address, its members and its settings.
What a feature is
A feature is one thing the hub can do for a workspace, such as keeping your documents, running AI personas, or tracking a project. A workspace has only the features it has been given, and you switch them on and off yourself. Some features bring others with them, because they need them, and a feature another one still needs cannot be switched off until that one goes first.
Every feature is documented the same way. Its first page says what it is. The pages after that take one part at a time. Its API card says what a program can do with it, and its Tech Detail card says why it is built the way it is.
The features
- Workspaces: the place you work in, and how it is set up and shared.
- Personas: AI personas you design and talk to, with the knowledge and memory you give them.
- Content: documents, notes, research and narratives, written in markdown and kept in versions.
- Projects: planning and tracking work.
- Storage: where your data is kept, and who can reach it.
- Ecosystems and products: the products you build, each with its own users, billing and settings.
- Teams, organizations and access: who works with you, and what they may do.
- Dashboards and monitoring: watching your sites, and the public status page.
- Community: discussions, messaging and notifications.
- Registries: public directories you publish, and others register in.
- Shipr: moving your code from testing to staging, and promoting it to production yourself.
- APIs and MCP: reaching all of the above from a program or an agent.
- Settings: your account, security, appearance, usage and subscription.
- The admin workspace: the console for the people who run the hub.
- The help site: where this documentation and the references live.
Under the hood
The pages after the features describe the platform the features run on. You do not need them to use the hub. They are there for when you want to know what happens behind a page.
- How it fits together: a page, a request, a sign-in and an agent's call, followed from start to finish.
- Authentication, identity and tenancy: who you are to the hub, and how your data is kept apart from everyone else's.
- The SQL schema: how the database is laid out.
- The AI processing node: the worker that runs AI jobs in the background.
- The pieces of the hub: the repositories, sites and services the hub is built from.
Terms
The glossary defines the words these pages use.
- APIs & protocols
- MCP
The database is the source of truth. The API, its documentation and its SDKs are all derived from the database schema, so what is documented is what is served and the two cannot drift apart.
One boundary keeps everyone's data apart. Every row of data says which ecosystem it belongs to, and the database itself enforces that a request sees only its own. The hub is just the first ecosystem, so developers and the end users of their products are kept apart in exactly the same way.
The mechanism sits below, the words sit above. The shared toolkit owns how a feature works; the hub supplies only what a host knows, such as its chrome, its workspace list and where sign-in lives.
Fail closed and reveal nothing. A workspace you cannot reach, a persona that is private, a repository you may not deploy: each answers as if it did not exist.
Derive, do not configure. One registry of sites is the single list behind routes, menus, sign-in origins and rail rows, because a hand-kept list drifts and a missing entry is a silent outage.
The owner deploys production. Every pipeline stops short of production until the owner promotes it.