robodev

DocsSign in

Start

Getting started

Create a Starbase project from the dashboard or CLI, then edit the hosted app.

Getting startedConnect a frontendStartersDatabaseDomainsFile-based APIsAuthEmailOrganizationsStorageSecretsPushSchedulesJobsDeployLocal developmentCLI reference

Robodev hosts a project as a file tree: schema, APIs, and an optional frontend on one host. Create an app from a starter in the dashboard (Create and deploy) or with robodev create. Edit in the Code page or locally. Signing up creates a personal organization; projects belong to that organization. Dashboard /login supports Google and password reset; that is control-plane login, not project-host Robodev Auth. Dashboard Profile (email, password, timezone, delete request) is the same control-plane account — it does not change project-host Auth users.

Dashboard prompt-to-build can use Grok or Gemini Flash. Choose the agent when you create the project; it cannot be changed later.

Install

terminal

npm i -g robodev

Or run commands with npx robodev without a global install.

First app

terminal

robodev auth
robodev create my-space-app
cd my-space-app/apps/fe
bun install
bun openapi:gen
bun dev
  • auth opens Starbase in the browser and stores tokens in ~/.robodev/credentials.json.
  • create makes a Starbase project, copies the chosen starter, writes .robodev (including a frontend block for Space, Auth chat, and Marketplace) and .env (including VITE_PUBLIC_API_URL), builds the Tiny SPA locally when bun/npm can, deploys, and runs npm install at the project root.
  • For Space, Auth chat, and Marketplace, a successful CLI frontend build hosts the Tiny SPA at the project App URL. Keep using bun in apps/fe (Vite default http://localhost:3000) to iterate locally. bun is required for apps/fe.

On a TTY, create lists starters. Pick Space, or pass --starter space to skip the prompt. Scripts without a TTY get space. Auth chat, Marketplace, and Backend are on the Starter page (/docs/starter).

What you get

  • A tiny database with planets, aliens, media, and planet_likes tables.
  • APIs at /api/planets, /api/planets/paginate, /api/planets/:id, /api/planets/:id/like, and /api/aliens/labels. Auth remains reserved at /api/user/*.
  • Swagger at https://{projectId}.robodev.povio.dev/_robodev/docs. API-only projects still serve Swagger at /docs.
  • A Povio UI in apps/fe (bun + Vite). After a CLI deploy with .robodev frontend set, the project host serves that built SPA. Dashboard create stays APIs only.

Next

Edit in the dashboard Code page and Save, or change files locally and run robodev deploy. Deploy uploads the allowed file tree (database.ts, api/, jobs, and frontend source when present). When .robodev has a frontend block, the CLI runs the local Vite build and uploads the static output. Destructive schema changes need confirmation or --force. Rename or permanently delete a project from Settings at /projects/:id/settings. Org admins can also set a Robodev URL or custom domain there; see Domains (/docs/domains).

Building the UI in Lovable, Bolt, or a similar tool? Open Lovable / Bolt on the project dashboard, generate a prompt, and paste it into the tool. That flow uses robodev-be (not the full robodev CLI). See Connect a frontend (/docs/frontend).