robodev

DocsSign in

Guides

Organizations

Projects belong to organizations. Members are admins or developers. Projects are unlimited on every plan.

Getting startedOffline dev with robodev devConnect a frontendStartersDatabaseDomainsFile-based APIsAuthEmailPDFOrganizationsStorageSecretsPushJobsSocketsMCP toolsLLMAgentsDeployArtifactsLocal developmentSelf-host a projectCLI referenceChangelog

Every signed-up user gets a personal organization named after their full name and is an admin of it. You can create more organizations, invite members as admin or developer, and switch organizations from the dashboard header. There is no owner role; multiple admins are allowed.

Roles

  • Developers can open projects, deploy (robodev deploy and the MCP publish tools), and use databases, Auth, Email, Storage, logs, and code. Developer is the role to give someone who should deploy.
  • Admins can also create, rename, and delete projects; invite and manage members; and rename or delete an empty organization.
  • The last admin cannot leave, be demoted, or be removed. Promote someone else first, or delete all projects and then the organization.

Invites

Admins invite by email. The accept page is /invite/:token. The invite email must match. If platform SMTP is unset, the dashboard still shows a copyable accept link.

Project members

A project can also be shared with people outside its organization, as admin or developer of that one project, on the project's Share page (/projects/:id/members), with robodev members, or with the MCP tools list_project_members, add_project_member, update_project_member and remove_project_member (on the hosted Robodev connector and robodev mcp). Adding needs a project admin. Someone with a registered Robodev account and a verified email is added at once and can deploy right away; anyone else (no account yet, or an unverified email) gets an email invite and has access after signing up with that email and accepting. Organization members already have access to every project of the organization: they show up read-only as Organization access, and are changed only on Organization → People. Every add, invite, role change and removal is in the organization's audit log. Managing members always needs a signed-in user; a deploy key gets 403 user_required.

Plans

Projects are not bound to a plan. An organization can have as many projects as it needs on Lite, Premium, and Scale alike, and there is no per-member fee. What a plan meters is tokens, and they are shared across the organization: when they run out, builds stop until the cycle refreshes or you buy a top-up.

Change a plan on Organization then Billing, or email robodev@povio.com. A request that would exceed a limit returns 403 plan_limit.

CLI

robodev projects lists every project you can access. On a TTY, robodev create asks which organization to use when you are an admin of two or more. Pass --org <id> to skip that prompt. With one admin org, or without a TTY, create omits the organization id so the API uses your oldest admin organization.