Company billing and usage controls
Move from self-serve usage based billing into a company-scoped usage path with predictable review points, usage reporting, and spend conversations before volume grows.
Xpersona Enterprise
Bring Xpersona to a company team without turning the rollout into a maze.
Enterprise access is for companies that want Xpersona /v1, native OpenCode setup, company billing, usage visibility, security review support, SSO scoping, and SLA options around real coding-agent work.
We keep the public path simple for self-serve builders, then add a company path when procurement, security, or volume needs make it useful.
Enterprise packet
Procurement-ready signals
Native OpenCodeProvider ready
Use Xpersona through the OpenCode provider flow or the standard /v1 endpoint.
Company rolloutGuided setup
Align API keys, usage visibility, model access, and billing before real production usage.
Security reviewEvidence path
Share architecture, data handling, status, and control notes during procurement review.
Fast enterprise brief
Model: frieren-coder. Base URL: https://www.xpersona.co/v1. Primary contact: support@xpersona.co.
What companies get
A serious path for teams, still simple enough to try.
Xpersona Enterprise is designed around the point where a developer tool becomes a company workflow: billing has to be accountable, access needs a policy, and security teams need clear answers.
OpenCode and /v1 rollout help
Give engineering teams a short path from API key to working coding-agent runs across OpenCode, scripts, and OpenAI-compatible clients.
Security and procurement support
Prepare a security-review packet with data-handling notes, privacy links, status visibility, and SOC 2-aligned control discussion without claiming certification before it exists.
Higher-volume access planning
Discuss workload shape, request limits, model routing expectations, support windows, and an SLA option that matches the real production path.
Security review
SOC 2, SSO, and SLA belong in the conversation.
Buyers search for those terms because they represent real procurement questions. We mention them clearly and honestly: review support now, scoped enterprise controls when a company needs them.
SOC 2 readiness discussion and security questionnaire support
SSO requirements scoping for company access
SLA options for production usage expectations
Data handling, privacy, and terms review
Usage, token, and spend reporting from dashboard surfaces
OpenCode provider and Xpersona /v1 integration guidance
Rollout path
Start with a pilot. Scale with evidence.
The best company adoption path is proof first: run a small workflow, confirm usage and value, then bring the security and billing packet into the buying process.
1
Intake
We learn the team size, coding-agent workflow, expected usage, and security review needs.
2
Pilot
A small team validates OpenCode, /v1, API keys, and dashboard visibility on real repo tasks.
3
Scale
Billing, support expectations, limits, and procurement evidence move into the company path.
FAQ
Enterprise questions, answered without pretending.
These are the questions a buyer, founder, security reviewer, or crawler should be able to understand from the page without chasing a sales deck.
Is Xpersona SOC 2 certified?
This page does not claim active SOC 2 certification. Enterprise conversations can include SOC 2 readiness, security controls, architecture notes, and the evidence needed for a buyer security review.
Does Xpersona support SSO?
SSO is handled as an enterprise rollout requirement. Tell us the identity provider and access model you need, and we will scope the right company-access path.
Can we get an SLA?
SLA terms are discussed for enterprise production usage. The right answer depends on request volume, support expectations, and the rollout shape.
Can a team start without enterprise procurement?
Yes. Start with usage based billing, create an API key, run a pilot in OpenCode or the Xpersona /v1 API, then move to enterprise when company billing or procurement review is needed.
Company access
Bring us the messy enterprise question. We will turn it into a rollout path.
Send the team size, expected usage, security review needs, and whether you want SSO or an SLA in the first scope.