For people
Browser interface
People write messages, manage boards, upload files, review generated media, approve requests, edit documents and inspect reports. Role-based access and audit records show who did what.
Business workspace · 70+ tools · one account
Raq.com puts team messages, tasks, files, e-signatures, support, CRM and 70+ AI tools in one account — with a browser for your team and an MCP interface for Codex, Claude Code and Supercomputer.
◆ open account your-account scope 75 tools · permissions applied → tasks.boards.list ok 4 boards → files.upload ok onboarding-brief.pdf → docs.render ok pack.pdf · 6 pages → esign.send hold approval required → tasks.cards.create ok RAQ-1184 ⧗ waiting on one human decision · everything else already recorded
01 — Why it exists
A chat product, a task board, a signing service, a file-sharing account, a form builder, a monitoring service and several AI subscriptions. Each one arrives with its own login, billing, permissions, data and audit history.
An AI agent becomes less useful when it can see only one piece of that setup. Raq.com puts those jobs in one account and gives agents a common route into them.
Accumulated
Raq.com account
1
One account, one permission model, one record.
Users can belong to more than one account and switch between them. Data, tools, permissions and AI usage are scoped to the selected account, and role-based access with audit logging shows who did what.
02 — Continuity
A single tool is useful on its own. The shared accounts are what allow longer workflows, because files, tasks, approvals, messages and project notes do not need a new integration for every pair of products. One worked example:
Step 01
Form Builder captures the enquiry with 17 question types and reports on responses.
Form Builder
Step 02
The workflow creates or updates the CRM record, opens an onboarding card and starts a client portal.
Automations · CRM · Task Board
Step 03
E-Sign sends the document from a template and keeps the audit record of the signature.
E-Sign
Step 04
The signed agreement and the client's uploads go into the account's files, linked from the project.
File Drop · Client Portal
Step 05
The agent reads the whole sequence, reports what is missing and asks for a decision where one is needed.
Supercomputer · Ask My Agent
Files, tasks, approvals, messages and project notes do not need a new integration for every pair of products. Agents can work across the account through one connection.
Where Raq.com differs
03 — Two surfaces, one record
Browser interface
People write messages, manage boards, upload files, review generated media, approve requests, edit documents and inspect reports. Role-based access and audit records show who did what.
Model Context Protocol
MCP gives an agent structured operations — list task boards, create a card, upload a file, run an image batch, read a project record. The agent does not need to imitate clicks when a direct operation exists.
Illustrative agent session. Operation names simplified.
// illustrative session — operation names simplified connect "raq.com/mcp" scope: account tools 75 available, permissions applied tasks.boards.list() → 4 boards files.upload(brief) → ok docs.render(pack) → 6 pages esign.send(agreement) → approval required tasks.cards.update(id) → ok // a person can see and amend all of it in the browser
04 — The public catalogue
Raq.com describes its public offer as 70+ tools. The list below groups the tools named in Raq.com's August 2026 product description; some fit more than one group.
75 tools listed
01
11 tools
02
11 tools
03
14 tools
04
8 tools
05
13 tools
06
8 tools
07
4 tools
08
6 tools
No tool in this list matches that filter.
05 — Agent operations
These products deal with execution, supervision, approvals, hand-offs and the record left behind. Supercomputer is the built-in route for people who do not want to configure a coding environment at all.
SC
Describe a job in plain English and let Raq.com's built-in agent choose and run the suitable platform tools against the same account, files and team.
Built in
OR
Runs templated, repeatable workflows across managed Codex and Claude sessions.
Repeatable
NW
Connects terminal sessions to a browser viewer so an operator can supervise work away from the desk, with keyboard and supported controller input.
Remote
HQ
A full-screen multi-terminal control room with keyboard controls and a live message queue.
Command view
PR
Separates work into human, mixed and agent-owned tasks so the operator can see where attention is needed today.
Daily view
✓
Tool access can be limited, and sensitive or external actions can require approval. Ask My Agent supports two-stage approval controls; Voice Calls is approval-controlled as well.
Controls
06 — Pricing
Per-user subscriptions. Every public tool is included in each paid plan, while AI usage and service limits increase with the plan. Prices exclude VAT where applicable.
Starter
£14per user / month
Website Build & Host is a paid per-site add-on on this plan.
Voice calls from here
Professional
£45per user / month
Voice Calls starts on Professional.
Business
£200per user / month
For larger teams and heavier service limits.
Enterprise
£500per user / month
The highest AI usage and service limits Raq.com publishes.
Custom Modules — managed extension
£190 per module / month, on top of a plan
On a paid plan, AI work draws from the account's monthly AI allowance, shown as AI usage rather than internal credit accounting. Different tools consume different amounts, so the pricing page gives examples per tool. If the allowance runs out, AI tools pause until renewal or a plan change; non-AI tools remain part of the subscription.
The total subscription changes as users join or leave the account. Customers can upgrade at once or schedule a downgrade for the next billing date. Annual billing currently receives a 5% discount. Monitoring tools and FinUK have plan-specific quantity limits.
New accounts receive a free trial with no card required. The trial allows one use of each AI tool and limited monitoring. Prices shown are per user, per month, and exclude VAT where applicable.
07 — Extension
Two separate extension models. The distinction matters because the commercial responsibility, runtime and support model are different.
| Criterion | 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 or $259 per month for each module, on top of a plan |
| Runtime | Sandboxed application hosted through the Custom Tools system | Native module inside the Raq.com product |
| Product fit | A self-built application embedded into the account | A first-class account-specific module in the normal sidebar |
| Maintenance | The customer owns the application work | Raq.com designs, builds, hosts, updates and maintains it while subscribed |
| Access | Draft and published visibility with scoped permissions | Explicit access for the customer's account and its team permissions |
| Agent access | Approved Raq.com operations through scoped MCP access | An MCP surface can be built into the module alongside its screens and workflows |
For customers who want their own coding agent to make an application. Each tool runs in an isolated container. Draft tools are limited to their creator; published tools can be shared with the account, and outbound access back into Raq.com uses approved, limited scopes.
This route suits a customer who can direct and maintain the build. Raq.com supplies the place to run it and the connection into the account, but does not provide the development work as part of the normal plan.
A managed software service. The customer describes the workflow, Raq.com reviews it and, when suitable, produces a first mock-up — normally within one working day, with a working module within five working days or less after approval. Larger jobs are identified during the mock-up stage.
The monthly fee covers design, development, hosting, maintenance and changes requested during the subscription. A module can use the account's tasks, files, contacts, documents and Automations, and connect to outside systems that provide an API. One module covers one area of work; a second module has a second monthly fee, although modules for the same account can share data. The customer's data stays in the account and can be exported.
08 — Privacy and security
Core text and chat requests use Zero Data Retention routes by default: under those routes the model provider cannot keep prompts or responses for training. A user can change the AI Privacy setting to reach models that do not support that protection, and live web search has its own setting.
Image and video tools send the prompt and required generation parameters to a specialist provider, and voice and transcription tools send the text or audio needed for the job. Those providers operate under their own API retention terms, so the text-AI statement should not be applied to every media tool. Raq.com states that it does not train models on customer content.
Customers assessing Raq.com for regulated or sensitive data should read the current Privacy Policy, AI Privacy & Security page and Subprocessors list, then map their own legal and sector requirements onto the specific tools they plan to use. Read the current policy on raq.com.
09 — An honest fit
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 need assessment.
Free trial · no card required