Supercomputer
The built-in agent. Describe a job in plain English and Supercomputer selects and runs suitable tools on the account — an agent route for people who won't configure a coding environment.
01 — One account · 75 tools
Raq.com is a business workspace with a browser interface for people and an MCP surface for agents — Codex, Claude Code, or the built-in Supercomputer. Messages, tasks, documents, signatures, media and monitoring, kept in one account and one shared record.
✓ raq mcp · 75 tools · scope: northwind-studio
task_board.create({ board: "Onboarding", card: "T-114 · proposal" })
→ ok · visible in the team's browser
e_sign.send({ file: "proposal-v3.pdf" })
⏸ awaiting human approval — Ask My Agent
$ ▌
02 — The platform
The browser is where people supervise. The MCP surface is where agents act. Both work against the same accounts, files, boards and records — so an agent's work stays inspectable, correctable and continuable by the team.
The human surface
Channels, boards, notes, files, approvals and reports. People write messages, review generated media, sign documents and inspect records with role-based access and audit history attached. Nothing about the browser is agent-shaped.
The agent surface
Raq.com exposes its tools through the Model Context Protocol: list boards, create a card, upload a file, run an image batch, read a project record. Where a direct operation exists, the agent doesn't imitate a human in a browser window.
The built-in agent. Describe a job in plain English and Supercomputer selects and runs suitable tools on the account — an agent route for people who won't configure a coding environment.
Prefer another client? Connect Codex, Claude Code or any compatible MCP agent and work against the same account — subject to permissions and approval controls.
Account-scoped access, limited tool access, and explicit approval for sensitive or external actions. Ask My Agent runs structured person↔agent exchanges with two-stage approval; Voice Calls is approval-controlled too.
Multi-step workflows across tools: react to an event, move data, ask AI to prepare material, send work for approval and continue after a decision — described in terms of your work, not a pile of scripts.
Built for agent operations
03 — The catalogue
Every paid plan includes the entire public catalogue — plans change your AI allowance and service limits, not your access. Search it, or see it by job.
No tool matches — try “board”, “media” or “privacy”.
04 — Continuity
Individual tools are useful. Shared records make longer workflows possible. Four routes teams actually take, start to finish.
A prospect completes an intake form.
An automation creates or updates the CRM record.
An onboarding card opens; a branded client portal is created.
The agreement goes out; the signed copy and client uploads land in the account's files.
Discussion stays on the board, and an agent can check the whole chain and prepare anything missing.
The team's rules live in one shared workspace.
A brief becomes a campaign plan with forms and automations.
Copy is drafted with sentence-level alternatives.
Media is produced in batches across models.
Decisions are collected; channel-specific posts publish after approval.
An AI agent designs, builds and hosts the site.
Reviewers pin written or voice comments on a frozen page.
The result is reviewed for search and AI visibility, then monitored for availability and content changes.
Incoming support is handled where it arrives.
Connects every alert to the responsible person.
A person records the desired outcome.
Starts the relevant agent workflow.
Active terminal sessions stay visible and supervisable.
The job pauses at a controlled boundary for a human decision.
Final files land in the workspace, and the task record carries the result and history.
05 — Extensions
They differ in who builds, who hosts and who maintains. The responsibility stays clear either way.
Self-built
Included with your plan
Your own coding agent builds an application that runs inside Raq.com, in an isolated container. Draft tools stay with their creator; published tools can be shared with the account, with approved, limited scopes back in.
Suits customers who can direct and maintain the work. Raq.com supplies the place to run it and the connection into the account.
Managed
£190 or $259 per module / month
A managed software service. You describe the workflow; Raq.com reviews it and normally produces a first mock-up within one working day — a working module within five working days or less after approval. Design, development, hosting, maintenance and requested changes are covered while subscribed.
One module covers one area of work with its own screens and data. Larger jobs are identified at the mock-up stage.
| Custom Tool | Custom Module | |
|---|---|---|
| Who builds it | The customer or the customer's coding agent | Raq.com and Vu |
| Price | Included with a Raq.com plan | £190 / $259 per month, per module, on top of a plan |
| Runtime | Sandboxed application on the Custom Tools system | Native module inside the product |
| Maintenance | The customer owns the application work | Designed, built, hosted, updated and maintained while subscribed |
| Access | Draft and published visibility, scoped permissions | Explicit access for the account, using its team permissions |
| Agent access | Approved operations through scoped MCP | An MCP surface can be built into the module |
06 — Plans
Every paid plan includes all public tools. Higher plans raise your AI allowance and service limits. New accounts start with a free trial — one use of each AI tool and limited monitoring, no card required.
£14/user · month
billed monthly
Most teams start here
£45/user · month
billed monthly
£200/user · month
billed monthly
£500/user · month
billed monthly
Per user, excluding VAT where applicable. Annual billing currently receives a 5% discount. Upgrade at once, or schedule a downgrade for the next billing date — the subscription follows your team as members join or leave. AI work draws from the account's monthly allowance; if it runs out, AI tools pause until renewal or a plan change, while non-AI tools carry on as part of your subscription.
07 — Privacy & security
Access is account-scoped, tool access can be limited, and sensitive or external actions use explicit approvals. The rest is stated plainly.
Core text and chat requests use ZDR routes by default — providers cannot keep prompts or responses for training. Live web search has its own setting.
Raq.com states that it does not train models on customer content, and separates its service records — kept for billing and reliability — from AI provider handling.
TLS 1.3 in transit. AES-256 full-disk encryption at rest on dedicated hardware — servers in Hetzner's German data centres for EU data residency.
Role-based access, audit logging that shows who did what, optional two-factor authentication, and UK GDPR-aligned handling.
Continuous monitoring with a defined incident-response process.
Image and video tools send prompts and parameters to specialist providers; voice and transcription send the media needed for the job. Those providers run on their own retention terms, and completed media is downloaded to Raq.com storage. Stated, not buried.
Assessing Raq.com for regulated or sensitive data? Read the current Privacy Policy, AI Privacy & Security page and Subprocessors list, then map your own legal and sector requirements onto the tools you plan to use.
08 — Honest fit
Raq.com doesn't claim feature-for-feature equivalence with every mature product. The value is breadth, the shared account and the agent layer across them.
In those cases, Raq.com can still sit around the existing system through Automations, APIs or a Custom Module — but the connection and compliance work deserve an assessment, not a promise.
75 tools, one account, a door for your agents and one for your team. Start with the free trial — no card required.