robodev

DocsSign in

Guides

Organizations

Projects belong to organizations. Members are admins or developers. Plans limit projects and members.

Getting startedConnect a frontendStartersDatabaseDomainsFile-based APIsAuthEmailOrganizationsStorageSecretsPushSchedulesJobsDeployLocal developmentCLI reference

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, and use databases, Auth, Email, Storage, logs, and code.
  • 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.

Plans

  • Free: 2 projects, 3 members.
  • Pro: 10 projects, 15 members.
  • Team: 50 projects, 50 members.

Paid plans are not self-serve. Use Contact to upgrade on Organization → Billing, or email robodev@povio.com. Hitting 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.