Your company’s own AI, for 60% less.

A private AI workspace at your firm’s own address, ai.yourcompany.com, and everyone gets it rather than the few people who could justify a licence. They can ask questions, draft and redraft, research, summarise documents, analyse files, work with spreadsheets and use approved firm knowledge. They sign in with the account they already have, through the directory you already run, so joiners get access and leavers lose it the same way everything else works.

By default Runvo hosts it, on single-tenant infrastructure in the region you choose. Runvo operates that deployment, which makes your firm the controller and Runvo the processor: which people at Runvo may reach your instance, what they may do there and how that access is logged are fixed by the engagement agreement, not by a page on a website. Nothing goes to another customer, and nothing is used to improve a product.

Yes, and that separation is what the word private is doing. Your deployment is single-tenant: your own instance, your own database, your own storage, your own keys, shared with no other firm. There is no pooled index and no shared document store sitting behind several customers at once. It runs in the region you choose.

No. Runvo does not train models and does not use your material to train anything. A request sent to a model provider is governed by the terms Runvo holds with that provider, and the providers behind your deployment are named in your agreement. If one of your own clients asks you this in writing, the answer is written down in a form you can hand over.

We tell you in writing before you sign, and again whenever it changes. The workspace reaches both frontier models and open-weight ones, and your people choose per piece of work rather than getting whichever model their subscription came with. Runvo is deliberately model-agnostic: what we agree with you is the quality bar, not a model name, because models are retired and repriced constantly and keeping up with that is a large part of what you are paying for.

Yes, and some firms have to, because their own client contracts say so. The same workspace is deployed into your own AWS, Azure or Google Cloud tenancy: you hold the infrastructure and Runvo’s access to it is whatever you grant. It costs more and it takes longer, because it runs at the pace of your access controls and your change process. If your contracts do not require it, the hosted default is faster and cheaper.

Per person it is 60% less than a premium per-seat licence, which is the whole reason the firm can put everyone on it instead of a shortlist. The number itself follows from headcount, so it is a sentence on a call rather than a table on a page: tell us how many people are in the firm and we will tell you what it costs, and it is agreed in writing before anything is built, and it does not move afterwards.

Per person on the workspace, and we agree that number before we start. You can open it to one department first if you would rather. But the price is set where it is so that you do not have to choose: the client work you cannot currently see is not confined to the people who would have put their hand up for a licence.

No. The price is flat per person and nothing inside the workspace is metered: no message caps, no per-token charges, no usage tiers. If you later point your own applications at the same infrastructure, that is priced separately, because the volume is then driven by software rather than by staff.

No. Runvo has no customers yet, no case studies and no references, and we would rather say so now than have you find out later. What we can do is show you a workspace running on a call, name the models it is calling and say where it is hosted. Anything published elsewhere under this name belongs to a different company.

A fair question to put to a company with no customers. Your material stays yours: it sits in an ordinary database and object storage in your own deployment, not in a format only Runvo can read, and it comes out. If that risk is the deciding one, deploying inside your own cloud tenancy removes it, because then the infrastructure is already yours and only the operating contract is ours. Ask us to write the notice period, the export and what happens to the instance into the agreement before you sign.

No. Runvo builds it, hosts it, secures it, updates the models underneath and runs it. There is nothing for your IT function to maintain beyond the identity provider it already runs, and no part of this turns your firm into an infrastructure team.

Hosting a model is the small half of the job. The larger half is the workspace around it: access through your directory, the tools people actually use, monitoring, scaling, security, model updates, and staff whose job it is to keep all of that running. Runvo does the whole of it against agreed targets for quality, latency, reliability and availability. If you want to own the infrastructure but not operate it, that is the own-tenancy option.

No, and this is not an argument about your subscription bill. Most firms keep the licences that are genuinely earning their keep and stop buying more, because the workspace covers everyone at a fraction of the price. What matters is that confidential client work moves onto something the firm controls; where the remaining licences sit after that is your decision.

No. Your people are already using it, on their own accounts, which is the reason to act rather than a reason to wait. Starting from nothing is simpler than starting from sprawl: there is no internal tooling to unpick, and the whole firm begins on the same workspace on the same day.

No. People open your firm’s AI and start working; it behaves the way they already expect AI to behave. What is new is the line about what may and may not go into it, and we brief your people on that when it opens.

Most firms are live within weeks of signing, because there is nothing for you to build: we deploy your instance, wire it to your directory, and open it at your own address for everyone on the same day. Inside your own cloud tenancy it takes longer, because it runs at the pace of your change process.