Unify City runtime and public services
Keep services, actions, auth, env, and studio boundaries inside one shared service city instead of rebuilding a backend per product.
Product · City SDK
Integrate the City runtime, Gate access, and public services into one shared service city for multiple studios.
Open City SDK Docs
Quick start, CLI, configuration, plugins, and operations live in the main docs.
Organize operations around the repo
Let service data, model records, accounts, usage, and payment state follow one reusable City boundary.
Keep local and team deployment aligned
Use the same City composition across local validation, Node deployment, and edge deployment.
Typical Scenarios
- • Shared service city: let multiple studios or products reuse accounts, models, usage, and payment services.
- • Gate access: call City from frontend, extension, or backend code without coupling to database internals.
- • Deployment composition: use cities/node or cities/edge for different runtime targets.
Facts
- • Core package: @downcity/city
- • Core source directory: packages/city/
- • Management entry: city manage