Supr.technology

Documentation

How Supr helps once you are inside.

Supr is a project workspace for founders and solo builders using supervised AI agents on real work. Create a project, assign a task, choose autonomy, review output, and keep usage and billing visible while the raw runtime stays protected behind the API boundary.

Create your account

Sign up, confirm your workspace, and start on the free path.

Make a project

Name the build, launch, repo, or workflow Supr should remember.

Submit a run

Describe the work, choose autonomy, and approve the plan when required.

Review the output

Use the result, inspect run history, and check usage before the next task.

1. Account setup

Start from the public site, create an account, and use a 12-character minimum password. New accounts begin on a free workspace with owner access. Sessions are held in httpOnly cookies from the API domain, which keeps browser access tied to the Cloudflare API layer.

After signup, the dashboard guides you toward the first meaningful action: create a project and give Supr a real task. The product is intentionally project-first because founders need help that remembers the build, not another answer floating in a chat tab.

2. Projects

Projects keep agent work organized around what you are building. A project can be a product launch, repo review, client build, internal tool, research sprint, or release cleanup pass. Create a project before submitting an agent run so context, metering, output, and history stay together.

Good project context includes the goal, the current state, relevant constraints, risk level, links, and what you want Supr to avoid. The clearer the project boundary, the easier it is to review whether the agent did useful work.

3. Agent runs

Agent runs are submitted from the dashboard and sent to the Worker API. Each request includes the workspace, project, plan limits, autonomy level, approval policy, project context, and prompt. The Worker checks billing, plan limits, and usage before proxying approved requests to the private Google Cloud runtime.

Use low autonomy for early exploration, planning, audits, and work where you want a plan before execution. Use higher autonomy only when the task is bounded, the output is reviewable, and the plan limits make sense.

4. Usage

Every submitted run uses one included agent task and creates a usage record. The Usage page shows task and model usage by billing period so you can see how much work Supr is doing and when a plan limit is close. Runtime is managed behind the scenes as an operational guardrail.

5. Billing

Billing uses Stripe Checkout for subscription starts and Stripe Customer Portal for subscription changes. Subscription status controls access to agent runs, including past-due, incomplete, and canceled states. Failed payments may limit new runs until the subscription is current.

6. Support

Support tickets can be created in the dashboard. Include the project, run ID, billing state, and error text when available so the issue can be tied to the right workspace history. For login, legal, privacy, or security issues that block dashboard access, use the public Support page.

7. Admin dashboard

The admin dashboard is restricted to platform-admin users. It exposes accounts, subscriptions, usage, agent runs, logs, plans, feature flags, support tickets, and system health without exposing raw runtime credentials.

8. Domains

9. Run states

10. First prompt examples

Good first prompts give Supr a boundary and a reviewable deliverable. Start with one of these, then add your project context inside the dashboard:

11. Troubleshooting

If a run is blocked, check subscription status, current usage, plan limits, autonomy level, project ownership, and whether approval is required. If the dashboard opens the full-screen agent but the runtime does not load, include the project, launch time, browser, and any visible error in a support ticket.