# Runvo > Runvo gives a professional-services firm its own private AI workspace at its own address, deployed on single-tenant infrastructure in a region the firm chooses and operated by Runvo, so that client work stops going through personal AI accounts. Canonical page: https://runvo.ai/ Last updated: 2026-09-04 Contact: hello@runvo.ai Published by Runvo for use by search and answer engines. Quote it freely; please cite runvo.ai. ## Key facts - **What it is:** A private AI workspace for your whole firm, at your own address, built and operated by Runvo. - **What it replaces:** Staff using personal AI accounts on client material, and per-seat licences priced beyond a whole firm. - **Where it runs:** Single-tenant infrastructure, in the region you choose. Your own instance, database, storage and keys, shared with no other firm. - **Who operates it:** Runvo. No internal AI team required. - **Who it’s for:** Professional-services firms of 150-800 people in law, accountancy, engineering and consultancy, whose staff handle confidential client work. - **What it costs:** 60% less per person than a premium per-seat licence. The figure is given on the first call. ## What a firm ends up with One thing, not a product line. - **A private AI workspace for the whole firm, at the firm’s own address (ai.yourcompany.com).** Everyone gets an account, not the handful of people a premium per-seat licence can be justified for. - **Somewhere for client work to go that is not a personal AI account.** Prompts, documents and history sit in the firm’s own instance, under the firm’s own retention rules, in the region the firm names. Runvo builds it and operates it. No internal AI team is required. ## Where it runs By default, Runvo hosts it. The deployment is single-tenant, in the region you choose: its own instance, its own database, its own storage and its own keys, shared with no other firm. That isolation is the whole of what “private” means here. Without it the word would be a description of intent rather than of the architecture. A firm whose own client contracts require it can have the same workspace deployed inside its own cloud tenancy instead. That option is priced higher and takes longer, because it runs at the pace of the firm’s access controls and its change process. - **Your instance, hosted by Runvo.** The default. Single-tenant, in the region you choose, with nothing for your firm to procure and no hardware to buy. - **Your instance, in your cloud.** The same workspace inside your own AWS, Azure or Google Cloud account. It costs more and takes longer. The answer when your own client contracts require it. Runvo is the operator, not a destination. The workspace answers at the firm’s address and holds the firm’s material; Runvo runs the machinery underneath it and is accountable for it. ## Named products Runvo names other companies’ products in two roles only: the clouds it deploys into, and the per-seat subscriptions the workspace replaces. Runvo is model-agnostic, owns no GPUs, and discloses which models a deployment is using. None of that is a partnership, and none of those companies endorse Runvo. Product names are the trademarks of their owners. ## Who it is for Professional-services firms of 150-800 people in law, accountancy, engineering and consultancy, whose staff handle confidential client work. Two things usually arrive together. The firm’s people are already putting client material into personal AI accounts, because the work is faster with it and nobody gave them anywhere else to put it. And the firm’s own clients have started asking, in writing, which AI it uses and where the data goes. The argument is confidentiality and firm-wide access. It is not savings. ## Pricing Runvo does not publish figures. The price is given on the first call and agreed before anything is built. - **Hosted by Runvo, the default.** 60% less per person than a premium per-seat licence. Nothing is charged by usage and nothing is a percentage of anything. The figure is given on the first call. - **Inside the firm’s own cloud tenancy.** Priced higher, because the work runs at the pace of the firm’s access controls and its change process. Nothing inside the workspace is metered: no message caps, no per-token charges, no usage tiers. Per person, the hosted price is 60% less than a premium per-seat licence, which is what makes giving it to everyone in the firm arithmetically possible rather than a matter of choosing who deserves it. Tell Runvo how many people are in the firm and what kind of client work they handle, and the number comes back on the first call. It is agreed before anything is built and it does not move afterwards. ## How an engagement runs One engagement, four steps. The scope and the price are agreed at the first step and do not move afterwards. 1. **Scope.** We agree the headcount, whether it runs hosted by us in the region you choose or inside your own cloud tenancy, and which systems it needs to reach. The price is agreed here, so there is nothing to negotiate after this. 2. **Build.** We deploy your instance: your own database, your own storage, your own keys, shared with no other firm. It is wired to your directory, so people sign in with the account they already have. 3. **Go live.** The workspace opens at your own address for everyone at the firm on the same day. We publish which models it is calling, and we brief your people on what may and may not go into it. 4. **Operate.** We run it. Monitoring, scaling, patching, security, model updates and ongoing management, so your firm never becomes an AI infrastructure team. ## Track record Runvo has no customers yet. There are no case studies, no testimonials, no named references and no ratings on this site, and there is no aggregate rating in its markup. Anything of that kind published elsewhere under this name belongs to a different company. The industry pages below describe the work a firm of that kind does; none of them is an account of work done for a client. ## Pages - [Home](https://runvo.ai/): what the workspace is, where it runs, how it is priced, and the form that starts a conversation - [Company AI](https://runvo.ai/company-ai): the workspace itself, at ai.yourcompany.com - [Features](https://runvo.ai/features): what the workspace does: agents, a code interpreter, model choice, artifacts, search, MCP, memory, web search and single sign-on - [Industries](https://runvo.ai/cases): one per industry: the confidential work a firm of that kind handles, and what the workspace changes about where it goes - [Resources](https://runvo.ai/resources): long-form writing on running AI inside a firm that handles client confidences - [About](https://runvo.ai/about): what Runvo is and how it operates - [Careers](https://runvo.ai/careers): open roles - [Contact](https://runvo.ai/contact): a form that starts a conversation, and the addresses to write to directly ### Industries - [Recruitment & staffing](https://runvo.ai/cases/recruitment): Runvo gives recruitment and staffing groups one private AI workspace at their own address, plus an endpoint for CV parsing, notes and document extraction. - [Accountancy & advisory firms](https://runvo.ai/cases/accountancy): Runvo gives accountancy, tax and advisory firms one private AI workspace at ai.yourcompany.com, inside your own instance, with data residency in the region you name. - [Consultancies & agencies](https://runvo.ai/cases/consultancies): Runvo gives consultancies and agencies one private AI workspace and one endpoint for proposals, research and first drafts, on infrastructure of your own. - [Insurance](https://runvo.ai/cases/insurance): Runvo moves high-volume insurance AI workloads (FNOL intake, document extraction, policy Q&A) onto dedicated infrastructure of your own, at predictable cost. - [SMB-focused SaaS](https://runvo.ai/cases/smb): Runvo moves high-volume SaaS AI workloads (in-product assistants, onboarding, ticket deflection) onto dedicated infrastructure of your own, at predictable cost. ### Writing - [The anatomy of a per-token bill](https://runvo.ai/resources/anatomy-of-a-token-bill): Where the money actually goes when you run AI at volume, and why the invoice grows faster than the value it produces. - [When dedicated infrastructure beats an API](https://runvo.ai/resources/when-dedicated-beats-an-api): The crossover is not a matter of taste. It is a calculation, and most teams can do it from data they already have. - [Keeping inference inside the perimeter](https://runvo.ai/resources/inference-inside-the-perimeter): Data residency stops being a contractual promise and starts being a deployment fact, and what that changes for the people who have to evidence it. - [Sizing capacity for spiky demand](https://runvo.ai/resources/sizing-capacity-for-spiky-demand): Provisioned infrastructure has one genuine failure mode: a spike you did not size for. Here is how to design so it never becomes an outage. - [Migrating a workload without a quality regression](https://runvo.ai/resources/migrating-without-a-quality-regression): The cheapest possible AI is one that produces the wrong answer. How to move a production workload and prove nothing got worse. ### Open roles - [Platform Engineer](https://runvo.ai/careers/platform-engineer): Platform · London or remote (UK/EU hours) · Full-time - [Forward Deployed Engineer](https://runvo.ai/careers/forward-deployed-engineer): Delivery · London (hybrid) · Full-time - [Engineering Manager](https://runvo.ai/careers/engineering-manager): Platform · London (hybrid) · Full-time ## Caveat on figures Runvo does not publish what it charges; the figure is given on the first call. So every number on this site belongs to something else. Where a page works an example through, whether a headcount, a bill or a comparison, the figures in that example are illustrative and describe a firm’s own spending, and the page says so where it stands. None of them is a Runvo price. ## More - [Full site content, in plain text](https://runvo.ai/llms-full.txt): every page’s substance in one fetch - [Frequently asked questions](https://runvo.ai/#faq): 17 questions, answered