01
Repo-native boundary
Every agent runs inside a real repository or folder. Skills are versioned, management config lives in one global DB, and runtime data stays in .downcity/.
Downcity
Scalable Agent Harness & Agentic Product Infrastructure for Builders.
One product is one City, where agents live and work. Every City is powered by shared models and services from the Federation.
Capabilities
Infrastructure for real agent products
Everything you keep rebuilding for every new AI product, organized into one reusable runtime layer.
02
Reusable runtime layer
Models, tools, tasks, memory, and services are configured once and reused across CLI, SDK, Console, and browser surfaces.
03
Plugin-native capabilities
Chat, Task, Memory, Shell, Web, Skill, Schedule, and Contact are all unified plugins that extend the agent without forking the core.
04
City-shared backend
Federation centralizes models, services, auth, and usage. Multiple Cities define product boundaries with distinct city IDs while their agents share the same runtime capabilities.
05
Operable agents
Run agents as managed daemons. Inspect status, review history, schedule tasks, and approve sensitive actions through CLI or Console.
06
Multi-surface deployment
Embed the same runtime into local CLI workflows, Node servers, Edge runtimes, or host applications with the Agent SDK and UI SDK.
Architecture
Creators build Cities. Users run them. Federation powers them.
A creator sets up shared services in Federation and ships a product as a City with its agents. The user runs that City locally and connects it back to Federation when shared capabilities are needed.
Philosophy
Runtime, not framework.
Downcity does not replace your stack. It gives agents a stable place to run, remember, and act—while products, tools, and humans stay in control.
Runtime as the reusable layer
Stop rebuilding model routing, auth, usage, and billing for every product. Configure them once in City and ship many surfaces.
Repo as the execution boundary
Agent behavior is grounded in the repository. Prompts, permissions, and artifacts travel with the code, not a distant platform.
City pays for the boring backend
Let City own accounts, balance, payment, model catalogs, and service routing so your product can focus on user experience.
Product shapes
One runtime. Many surfaces.
The same Downcity backend can power very different product experiences.
CLI productivity tool
A repo-local agent that summarizes code, runs tests, and manages tasks from the terminal.
Browser extension agent
An agent that reads the current page, takes notes, and acts on behalf of the user through web tools.
Embedded SDK workflow
Drop the Agent SDK into an existing app to add long-running sessions, memory, and plugin-driven actions.
Multi-tenant product backend
Use City to share auth, usage, and billing across customer-facing agents deployed on Node or Edge.
Start building with Downcity
Install the CLI, create your first agent project, and connect to City in minutes.