Individual
PreviewFor an owner exploring the governed-project model.
Pricing not publishedPlan definition in developmentGet started- Intended audience only
- Limits are not published
- Commercial availability is not announced
Priced around accountable teams.
A plan should reflect the project boundary, the people responsible for decisions, and the controls the work needs. Public prices and commercial terms are not yet published.
A clear structure, before the numbers.
These tiers describe intended audiences only. They do not promise availability, features, limits, or commercial terms.
Team
PreviewFor shared delivery with durable membership and role boundaries.
Pricing not publishedIdentity milestone requiredGet started- Intended audience only
- Membership model remains in development
- Entitlements are not published
Enterprise
PreviewFor organizations evaluating governance and deployment requirements.
Pricing not publishedScope by requirementsGet started- Intended audience only
- Deployment terms are not committed
- Commercial terms are not published
The work defines the boundary.
The supplied pricing concept organizes plans around a team rather than prompt volume. That direction remains provisional until the commercial model is approved.
- 01Scope the work first
The product model starts with the brief, its authority boundaries, and the team the work requires. Final commercial packaging remains a product decision.
- 02Keep governance visible
Owner approval and independent review remain part of the governed operating model. Plan-specific entitlements have not been approved.
- 03Publish limits before sale
Project, member, retention, support, deployment, and integration terms will stay unpublished until they are approved and supportable.
What is known today.
A status-led comparison keeps product direction separate from unapproved commercial commitments.
| Commercial field | Individual | Team | Enterprise |
|---|---|---|---|
| Intended audience | Solo owner | Shared team | Organization |
| Public price | Not published | Not published | Not published |
| Commercial availability | Not announced | Not announced | Not announced |
| Account model | In development | In development | Requirements pending |
| Plan limits | Not published | Not published | Not published |
| Deployment terms | Not published | Not published | Not committed |
Pricing questions, answered plainly.
Are vbxns prices published?
No. Public prices, billing periods, plan limits, trials, and commercial terms have not been approved. This page describes the intended audience structure without presenting an offer for sale.
Can I create a paid account today?
No. The current sign-up surface is informational while open registration, durable identities, account creation, memberships, and revocable sessions remain in development.
What will each plan include?
Plan-specific entitlements are not published. The repository supports the governed product model, but project limits, member limits, retention, support, integrations, and deployment options require approval before they can be promised.
Are named integrations included?
No live vendor integration is claimed. The public product direction describes categories of approved tools that may enter a project boundary; named availability will require implementation and verification evidence.
Does the governance model change by plan?
The documented product model keeps owner authority, least privilege, recorded decisions, and independent review as governing principles. How those controls are packaged commercially has not been decided.
Is private or dedicated deployment available?
No deployment option is being offered on this page. Enterprise deployment requirements and commercial terms remain uncommitted until they are approved and operationally supportable.
Start with the current access path.
See what is available now, what remains in development, and where the production boundary stands.