▲ FAQ
Questions, answered.
Pricing, security, infrastructure, the Frontend Helper. If yours isn't here, drop us a line.
01 Do I need to host my own infrastructure? +
No. You can start on staff.rip's included infrastructure on any paid plan. But if you want to run agents on your own machine or point Spaces at your own servers, you can — just run staffrip-agent wherever your code lives.
02 How does staff.rip handle AI costs? +
Three options, switchable per organisation. (1) Bring your own provider API key (Anthropic, OpenAI, others as we add them) — the LLM spend goes through your account, staff.rip never sees it. (2) Connect your existing Claude account directly. (3) Use the bundled staff.rip provider, which routes across upstreams to keep cost down — Pro plans include a free monthly AI token allowance for coding, with metered usage above that.
03 Is my code safe? Can staff.rip read my codebase? +
Agents only access the filesystem paths you configure per Space. Context is isolated per Space — no agent can read files from another Space. You control what tools each agent can use via MCP configuration.
04 What is the Frontend Helper and how do I install it? +
It's a lightweight JavaScript widget you embed on any page you're already running — your local dev server, a staging URL, a Vercel preview. One script tag, no framework dependency. It phones home to your workspace's agent over WebSocket.
05 Does staff.rip work with any framework or language? +
Yes. Spaces are just directories. Your agent can run any command, work with any language, and talk to any service you configure via MCP. The Frontend Helper works on any HTML page.
06 What happens if an agent makes a mistake? +
Agents write to your filesystem through staffrip-agent, which means you have full git history. Before any significant operation, agents can be configured to ask for confirmation. The Frontend Helper's annotation lifecycle means changes are scoped, reviewable, and attributed.
07 Can multiple people use the same Space? +
Yes. Spaces support multiple concurrent sessions and are visible to all org members with access. Real-time sync means everyone sees the same board, chat, and agent state.
08 What is a worker exactly? +
A worker is an instance of staffrip-agent — a running daemon connected to your workspace. It's the bridge between a Space's agent and your local filesystem. One worker can handle one active agent session at a time.
09 Can I use staff.rip without any AI — just as a project management tool? +
The workspace is built around AI agents, but boards, spaces, chat, and file management all work without an active agent session. You won't get the full value, but the structure is there.
10 What models does staff.rip support? +
Claude is the default. You can also bring your own provider key (Anthropic, OpenAI, more as we add them) or connect your existing Claude account. The bundled provider may route across upstreams behind the scenes to optimise cost — your workflow stays the same.
11 How does the reseller programme work? +
Approved resellers get a dashboard to create and manage downstream organisations. You set client pricing, staff.rip invoices you at wholesale, you invoice your clients. Granular controls let you cap workers, spaces, and tunnels per client org.
12 Is there an on-premise or self-hosted option? +
The agent daemon (staffrip-agent) runs on your own hardware today. Full self-hosted deployment of the platform is on the enterprise roadmap. Talk to us.
13 What's the difference between the free and Pro plans? +
The free plan caps you at 1 worker, 5 spaces, and 1 member, with VPS and tunnels available pay-as-you-go once you add a payment method. Pro is €15 per active user per month and unlocks 100 workers, 10,000 spaces, 1,000 tunnels, unlimited members, plus per-seat allowances: 1 included tunnel, 1 DEV1-S VPS, and a free monthly AI token allowance for coding.
14 Can I cancel at any time? +
Yes. Monthly billing, no contracts, cancel from your org dashboard. Your data is exportable.