Business workspace
Raq.com is one account for people, teams and AI agents. More than seventy business and AI tools share the same files, tasks, permissions and history — so an agent can finish what a person started, and the team can inspect the result.
No card required. The trial includes one use of each AI tool and limited monitoring.
Continuity
Small teams often assemble an operating system from chat, boards, signing, files, forms, monitoring and several AI subscriptions. Each has its own login, billing, permissions and history. Raq.com keeps those jobs in one account so an agent is not trapped inside a single slice of the work.
Work starts in Team Comms or as a card on a Task Board, with a person or an agent as owner.
Source material lives in File Drop and Project Base. Agents read the same records the team can see.
Pretty Docs, Ghostwriter or Contract Auditor produce the artefact against the account’s files and notes.
Sensitive or external actions wait. Ask My Agent and Voice Calls use explicit, staged controls.
The board, the portal and the audit trail keep the result where the team can inspect, correct and hand off.
One workspace
The browser and the agent surface write to the same records. A person can amend work an agent created. An agent can continue work a person started. Access is account-scoped, tool access can be limited, and the team still has ordinary interfaces for review.
Work belongs to an account — a person, company, client or project group. People switch accounts, write messages, manage boards, upload files, approve requests, edit documents and inspect reports under role-based access.
Compatible agents connect through the Model Context Protocol. They get structured operations — list boards, create a card, upload a file, run an image batch — instead of imitating clicks. Supercomputer, Codex, Claude Code and other compatible clients work against the same account.
Agent operations
Raq.com treats agents as operators. Supercomputer picks tools from a plain-English job. Automations and Orchestrator run longer work. Nature Work and Agent Operator HQ keep a human in a position to supervise, approve and take the record back.
The built-in agent works with the same account, files and team as connected external agents. Non-technical users get an agent route without configuring a coding environment.
Templated workflows run managed sessions. Priorities then separates human, mixed and agent-owned tasks so an operator can see where attention is needed.
Local sessions connect to a remote viewer with keyboard and supported controller input — built for execution and hand-off, not ordinary chat.
How it hangs together
A single tool can be useful on its own. Shared records are what let a process run across the account without a new integration for every pair of products.
Catalogue
Raq.com does not claim feature-for-feature equivalence with every mature specialist product. The value is the breadth of useful tools, the shared account, and the agent layer across them. Keep specialist systems where you need them and connect them through APIs, Automations or a Custom Module.
Extensions
Two separate models. The commercial responsibility, runtime and support are different — and that distinction is deliberate.
| 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 / month per module, on top of a plan |
| Runtime | Sandboxed application in 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 |
For customers who can direct and maintain a build. Each tool runs in an isolated container. Draft tools stay with their creator; published tools can be shared with the account. Outbound access back into Raq.com uses approved, limited scopes. Raq.com supplies the place to run it and the connection into the account — not the development work.
A managed software service. Describe the workflow; Raq.com reviews it and, when suitable, produces a first mock-up — normally within one working day — and a working module within five working days or less after approval. Larger jobs are identified at mock-up. The monthly fee covers design, development, hosting, maintenance and changes. One module covers one area of work.
Plans
Per-user subscriptions. AI usage and service limits increase as you move up. Prices exclude VAT where applicable. Annual billing currently receives a 5% discount.
per user / month
per user / month
per user / month
per user / month
On a paid plan, AI work draws from the account’s monthly AI allowance. Raq.com shows this as AI usage rather than internal credit counts. If the allowance runs out, AI tools pause until renewal or a plan change; non-AI tools remain. Different tools consume different amounts — a short rewrite, a multi-model report and a generated video are not equivalent. Monitoring tools and FinUK have plan-specific quantity limits.
Custom Modules
Design, development, hosting, maintenance and changes while you remain subscribed. AI features on a module use the account’s normal AI allowance. A second area of work is a second module.
per module / month, on top of a Raq.com plan
Privacy and security
Raq.com separates how it handles core text and chat from image, video and voice providers. It does not train models on customer content. Customers assessing the service for regulated or sensitive data should map their own requirements onto the specific tools they plan to use.
Core text and chat requests use Zero Data Retention routes so the model provider cannot keep prompts or responses for training. You can change the AI Privacy setting to reach models that do not support this protection. Live web search has its own setting, because a current-information lookup may need a standard provider route.
Image, video, voice and transcription tools send the prompt or media the job needs to specialist providers under those providers’ API retention terms. Completed media is downloaded to Raq.com storage. The text-AI Zero Data Retention statement should not be applied to every media tool.
Data in transit.
Full-disk encryption at rest on dedicated hardware.
Dedicated servers in Hetzner’s German data centres.
Aligned handling, with role-based permissions and audit logging.
Optional two-factor authentication for user accounts.
Continuous monitoring and a defined incident-response process.
Fit
The product is a good operating layer for teams that want fewer logins and an inspectable agent record. It is a weaker fit when a specialist system must remain the system of record, or when a regulatory requirement has not been validated against current controls.
In those cases Raq.com can still sit around the existing system through Automations, APIs or a Custom Module. The connection and compliance work need assessment.
Company
Raq.com is built by Vu, an AI and software company based in Solihull. Vu uses Raq.com for its own work and builds the managed Custom Modules. Phil Webb is CEO and co-founder. Alex Hawke is CTO and co-founder and leads the product and engineering work.
CEO and co-founder
CTO and co-founder · product and engineering
Get started
New accounts receive a free trial with no card required. Paid plans include the public catalogue. Connect Supercomputer, Codex or Claude Code when you are ready to put work on the record.