Follow a fictional company through the real decisions OneClient is designed to make simpler, safer, and more legible.
Northline is a fictional composite used to show the OneClient workflow—not a customer testimonial. Its founders have a mobile app, a web dashboard, and one week to test an idea. They create an organization and a project. OneClient produces isolated development and production environments; production remains protected until they deliberately subscribe.
The team enables email OTP and magic links, sets trusted callback origins, and uses the browser client. Their data policy allows people to read their own profile and denies everything else. A private preview is already available; there is no public half-configured backend to find.
Northline connects the OneClient MCP server with a project-scoped token. The agent reads the OpenAPI contract, creates a migration, adds an object upload, and deploys a preview. It never receives a raw database, storage, email, or infrastructure credential.
The team reviews one immutable deployment, configures app.northline.example and api.northline.example, activates a plan, and promotes. Auth follows the approved API host. TLS and routing state remain visible in the console.
Included credits are consumed first. Northline sets alert thresholds and a hard project ceiling, then adds prepaid credits during a launch. Managed AI calls declare maximum output and reserve the worst-case price. Every debit points to a price version and usage event.
More projects, queues, scheduled work, analytics, and email templates arrive behind the same SDK. The team can export data, rotate keys, review the audit trail, roll back deployments, and understand its bill without becoming an infrastructure operations company.