Packaging & Tiers
Adopt the formal layer through open entry, team workflow, and enterprise controls.
CLI is public. Team and enterprise routes add shared review, identity, deployment, and audit posture.
Open route
FreeCLI + docs
Start locally without commercial setup.
Team route
BetaShared review
Shared dashboard, audit, and collaboration.
Enterprise route
CustomEvaluation
Deployment and identity are scoped in review.
Packaging Model
Four routes, different workflow depth
Free
For developers exploring CLI, SDKs, and local review.
- CLI and SDK access
- Core and extended monomer catalog
- Supported export targets
- Public documentation
- Public registry read
- Local lift and check
- Community support
Pro
For teams testing private workflow surfaces.
- Everything in Free
- Private circuits and rows
- GitHub integration
- PR verification status
- Certification dashboard
- Priority support path
- Shared team collaboration
Team
For groups needing shared review and governance.
- Everything in Pro
- Shared dashboard
- Team audit trail
- Role-based access control
- Organization integration
- Slack / webhook notifications
- Governed review loops
Enterprise
For scoped identity, deployment, and evidence review.
- Everything in Team
- SSO / SAML / OIDC
- SCIM provisioning
- Evidence packages for audit
- Private registry posture
- CI/CD gate plugins
- Self-host posture review
- Dedicated support
Platform, compliance, and support scope depend on the route you enter.
Feature Comparison
Detailed comparison by workflow area
| Process Area | Free | Pro | Team | Enterprise |
|---|---|---|---|---|
| Core | ||||
| CLI access | ||||
| Core + extended catalog | ||||
| Supported export targets | ||||
| Local lift/check workflow | ||||
| Public docs | ||||
| Platform | ||||
| Public registry | ||||
| Private registry | ||||
| GitHub integration | ||||
| Verification dashboard | ||||
| PR verification status | ||||
| Team seats | 1 | Up to 10 | Up to 50 | Scoped |
| Team & Governance | ||||
| Shared dashboard | ||||
| Team audit trail | ||||
| Role-based access | ||||
| Org-level integrations | ||||
| Slack / webhooks | ||||
| Enterprise | ||||
| SSO / SAML / OIDC | ||||
| SCIM provisioning | ||||
| Evidence packages | ||||
| Self-host posture | ||||
| SLA review | Yes | |||
| Dedicated support engineer | ||||
| Support | ||||
| Community support | ||||
| Email support | ||||
| Priority support | ||||
| Architecture review | ||||
Commercial FAQ
Common questions before rollout
Q.Can I use BRIK64 without the platform?
Yes. CLI and docs are the open entry path. Platform matters when teams need shared review, publication, or private collaboration.
Q.What languages are supported?
Use the current CLI and SDK docs as source of truth. Supported paths can evolve during beta.
Q.What does 'certified' mean here?
It means the modeled circuit passed declared checks under bounded domains. It is not a blanket infrastructure or compliance claim.
Q.Is there academic pricing?
Academic evaluation is handled directly. Send institutional context to hello@brik64.com.
Q.Can I self-host?
Self-host posture is scoped during enterprise evaluation. It depends on deployment, identity, and review workflow.
Q.Does BRIK64 store my source code?
The public CLI path is local-first. Platform workflows center on blueprints, hashes, and review state.
Q.What happens after beta?
The CLI path stays public. Paid packaging will be published when scope is stable enough to document.