One account. One organization. One subscription.
Virex products share identity, organizations, seats, and billing. Adopting a second product is a seat toggle rather than a procurement cycle, and the security model does not change when you do.
// Coordination and state on our side. Code and execution on yours.
Built for teams from the first login.
Organizations, member management, and per-product seats are core mechanics here, not enterprise add-ons bolted on later.
Unified identity across every host
One login covers the marketing site, your organization administration, the product portal, and the auth portal. Sessions are managed server-side, so browsers never handle tokens.
One organization per user
Each user belongs to exactly one organization. That keeps access, billing, and data ownership unambiguous, and it suits small and mid-size teams without a tenancy puzzle.
One subscription per organization
Your organization holds a single subscription containing one item per product. Products are subscribed independently and billed together, so finance sees one line of thinking rather than several.
Seats grant access
Holding a seat on a product is what lets a member use it. Admins assign and adjust seats per member per product as the team changes.
A control plane, not a compute cloud.
Virex coordinates with the agents and tooling installed on your machines. It carries state and control signals. It does not run your work.
Your machines execute
Agents run where you installed them. Virex Remote maintains a live link to the session; Claude Code itself keeps running locally throughout.
Your credentials stay put
Model subscriptions and machine credentials remain on your side. Virex does not resell tokens or route your agent through a vendor runtime.
We carry the signals
Session activity, decisions, memory writes, and entitlement state travel through the control plane so every surface you use agrees on what is happening.
What the architecture guarantees.
Stated plainly, with no claims we cannot back.
Full detail lives on the security page.
Every client is ours.
MCP servers, CLIs, SDKs, and web apps are all built by Virex. When an integration breaks, it is our bug to fix rather than a third party's roadmap item.
MCP servers
Both products expose a first-party MCP surface so agents can use them as tools. Virex Memory reads and writes memory; Virex Remote drives sessions.
CLIs with device-flow login
Terminal sign-in uses a device flow, so there are no long-lived tokens pasted between machines.
SDKs and APIs
Virex Memory exposes REST and gRPC APIs on one host, alongside first-party SDKs for teams wiring memory into agents they built themselves.
Setup instructions and reference material live in the docs.
Platform questions
What does control plane mean in practice?
It means Virex holds the coordination layer and nothing else. Your agent runs on your machine under your own model subscription. Virex tracks session state, relays your decisions, stores memory, and enforces entitlements. It never executes your code.
How do seats work across two products?
Seats are per member, per product. A member with a Remote seat and no Memory seat can use Remote only. Admins change seat counts at any time, and the subscription reflects the change on the matching line item.
Can a user belong to more than one organization?
No. Each user belongs to exactly one organization. If you need a second organization, that is a second account.
How is one organization kept separate from another?
Isolation is enforced at the database layer through row-level security, so a query for one organization cannot return another organization data even if application code is wrong.
Is Virex SOC2 certified?
No. The security controls are designed to a SOC2-oriented control set, and the architecture is built with an audit in mind, but no audit has been completed and there is no certification to claim.
What happens to product access when someone leaves?
An admin removes their seat. Access to the product stops with the seat, and the organization keeps the data the member wrote.
Start with one product. Add the other when it earns it.
Create your organization, subscribe, and assign seats. The account model is the same either way.