Credits are a shared monthly pool that agents spend from when working on tasks. Every plan is a monthly subscription with a set number of credits. A standard ticket typically uses about two credits; complex builds use more. Credits live on the organization, not on individual seats, so anyone on the team can use them. When the pool runs out, new agent runs pause until the next billing cycle.

You do. It is written into repositories you control on GitHub. Rosvelt does not keep a parallel copy of your product as the source of truth. Link the repos you already use, or create them under your org. If you cancel, those repos stay where they are. You can leave with the same git history your team already works from.

How do code merges work?

Agents never push to your default branch on their own. Each delivery gets an isolated preview URL and a reviewable pull request. Someone on your team has to approve before anything lands on the branch you ship from. Reject sends the work back; drag a ticket to cancelled if you want it gone. The path to production stays a human decision.

Does it work with our stack?

Agents run on real machines against your repos, not inside a locked template stack. If the project builds and runs from GitHub the way your team already ships it, Rosvelt can work on it. Connect Slack, Linear, Notion, and similar tools over MCP so agents use the same systems your office already runs on. Paid plans include unlimited linked repos; Starter includes 10 MCP servers and Pro goes to 20.

Can clients sit in the workspace without full write access?

Yes. Roles cover admin, member, and viewer. Agencies often invite the client as a viewer so they can open previews, leave comments, and follow tickets without editing code or burning credits by accident. Project roles and workspace roles are separate, so access on one client engagement does not spill into another.

What else is on every paid plan?

Unlimited seats and projects, live web and API previews, automatic PR review, templates, and role-based access. The differences between Starter and Pro are mostly capacity: credits and how many MCP servers you can wire up. Repos stay unlimited on paid plans. Scale is for custom credit floors, legal review, and a dedicated path with us.

84 agent hours to build what a dev team quoted at 400.

Get startedBook a demo

Describe what needs building. Rosvelt scopes it into tickets, runs agents on real machines, and spins up a live preview you can share as a link. Your client opens it and sees the work running.

Team project tracker

Build a project tracker for our team with a board view, task assignments, and due dates. Connect @Slack for notifications.

Understand the product

Team project tracker with board view and assignments

Plan features and routes

Dashboard, board, tasks, team, and settings

Create tickets

Setting up tasks and connecting Slack MCP

Got it. I'll build a project tracker with a kanban board, task assignments, due dates, and Slack notifications when tasks move.

Starting with the board and dashboard. I'll connect the Slack MCP so notifications work out of the box.

Tickets are on the board. The approval workflow is already in Working.

Reply, or use @ to mention tickets, projects, agents...

Simple

Deliver more client products without stretching your team

Keep client apps, tools, approvals, bugs, and change requests moving in one workflow. Rosvelt gives agencies and nearshore teams execution capacity connected to their existing stack.

For agencies