Skip to main content
The Apps API provides full lifecycle management for managed web applications. Each app is backed by managed hosting; fullstack apps additionally get a dedicated managed backend (PostgreSQL, auth, storage, edge functions). Naive owns the underlying credentials and injects them into every call. Apps can be frontend_only (static/Next.js) or fullstack (Next.js + managed backend). Apps are fully standalone — no agent orchestration required. Build locally from a starter template and deploy by uploading your project; or, when the company has an agent container, let engineer agents build and deploy from their workspaces.

​
Capability Model

Two layers of access:
  1. Lifecycle endpoints — curated, opinionated operations for the common path: create, deploy, publish, secrets, domains, database queries.
  2. Provider proxies — generic passthrough to the underlying hosting REST API and backend management API, scoped to the app’s own project. Anything those APIs support — build logs, project settings, auth config, storage, edge functions, migrations — works through the proxies.

​
Endpoints

​
Capability Primitives

A fullstack app’s managed backend is also exposed as four first-class primitives, each a curated surface over these proxies (and individually gateable in Account Kits):

​
Per-User Scoping

All routes are also mounted under /v1/users/:user_id/apps for multi-tenant setups. On the per-user mount, the subject’s Account Kit must enable the apps primitive, and every :id route verifies the app belongs to that user.

​
Authentication

All endpoints require either a session cookie or a Bearer API key: