Skip to main content

Documentation Index

Fetch the complete documentation index at: https://usenaive.ai/docs/llms.txt

Use this file to discover all available pages before exploring further.

Apps are Vercel-backed web applications that your AI agents can build, deploy, and maintain. Each app gets its own Vercel project, optional Supabase database, and a dedicated engineer agent that operates autonomously via the kanban task system.

​
CLI First

# Create and deploy a landing page
naive apps create --name "My Landing Page" --type frontend_only
naive apps deploy <app-id>
naive apps publish <app-id> --deployment <deployment-id>

# Create a fullstack app (adds Supabase)
naive apps create --name "My Product" --type fullstack
naive apps db tables <app-id>
naive apps db query <app-id> "SELECT * FROM users LIMIT 5"

​
App Types

TypeInfrastructureUse Case
frontend_onlyVercel (Next.js)Landing pages, marketing sites, static apps
fullstackVercel + SupabaseSaaS products, dashboards, apps with databases

​
How It Works

  1. Create — naive apps create provisions a Vercel project (and Supabase for fullstack). A dedicated engineer agent is assigned.
  2. Build — The engineer agent builds the app code in its workspace, guided by task descriptions from the CEO or manual instructions.
  3. Deploy — naive apps deploy pushes the workspace code to Vercel as a preview deployment.
  4. Publish — naive apps publish promotes a preview to production, making it live on the app’s domain.
  5. Iterate — Deploy again, manage secrets, connect domains, and continue building.

​
Creating an App

naive apps create --name "StudyAI" --type fullstack --description "AI study assistant"
Returns the app ID, Vercel project details, and the default production domain (e.g., naive-studyai-abc123.vercel.app). For fullstack apps, Supabase provisioning starts immediately in the background. The database URL and anon key are automatically injected as environment variables.

​
Deployment Workflow

​
Preview Deployment

naive apps deploy <app-id>
Pushes the current workspace code to Vercel. Returns a unique preview URL that you can test before going live.

​
Promote to Production

naive apps publish <app-id> --deployment <deployment-id>
Promotes a preview deployment to the production domain. Traffic is switched immediately with zero downtime.

​
Deployment History

naive apps deployments <app-id>
Lists all past deployments with status, URL, and whether each is the current production version.

​
Environment Variables

Manage environment variables that sync to Vercel: 
# Set a variable for preview deployments
naive apps secrets set <app-id> STRIPE_KEY sk_test_... --target preview

# Set for production
naive apps secrets set <app-id> STRIPE_KEY sk_live_... --target production

# List all keys
naive apps secrets list <app-id>

# Reveal a value
naive apps secrets reveal <app-id> STRIPE_KEY --target production

# Delete
naive apps secrets delete <app-id> STRIPE_KEY --target preview
For fullstack apps, NEXT_PUBLIC_SUPABASE_URL and NEXT_PUBLIC_SUPABASE_ANON_KEY are automatically provisioned. You don’t need to set these manually.

​
Custom Domains

Connect your own domain to an app: 
# Add a custom domain directly
naive apps domains add <app-id> myapp.com

# Or connect a company domain (purchased/registered via naive domains)
naive apps domains connect <app-id> <domain-id>

# Verify DNS after configuring records
naive apps domains verify-dns <app-id> <domain-id>

​
Database (Fullstack Only)

Fullstack apps include a Supabase PostgreSQL database: 
# List tables
naive apps db tables <app-id>

# Run queries
naive apps db query <app-id> "SELECT count(*) FROM users"
Use the Supabase client in your app code for real-time queries, auth, and storage. The connection details are available as environment variables.

​
Retry Failed Provisioning

If Vercel or Supabase provisioning fails (e.g., rate limit, network issue): 
naive apps retry <app-id>

​
Deleting an App

naive apps delete <app-id>
This immediately removes the Vercel project, Supabase project (if fullstack), all secrets, domains, and the associated engineer agent.

​
Agent Integration

When the CEO creates a plan that includes apps, it:
  1. Creates apps with naive apps create
  2. Hires engineer agents assigned to each app
  3. Creates tasks with explicit deployment instructions
  4. Workers build the code and run naive apps deploy + naive apps publish automatically
The task description always includes the app ID and deploy commands so engineers know exactly how to ship their work.