FREEPLANNED
Not yet set
ANNOUNCED BEFORE RELEASE
Students, evaluators, open source
- Core IDE, fully usable
- Limited completions and chat
- Local analysis
- Small monthly Mission credits
- Community support
PRICING // PLANNED
Planned pricing for verified outcomes, not tokens.
Astvyr has not been released. What follows is planned packaging, not a price list: prices are not yet determined and will be published before the planned release on 7 July 2027. Usage will be metered where the work actually costs money: agent compute, sandboxes, Twins, evidence retention, release control, private runners and marketplace.
PRE-RELEASE // IN DEVELOPMENT · PRIVATE TESTING
Astvyr has not been released. The product is in development and under private testing; the planned release date is 7 July 2027. Early access is not provided and no builds are published. Prices are not yet determined. Nothing on this website is an offer, a promise of availability or a commitment to any date.
PLANNED POLICY: NO SURPRISE OVERAGE FOR INDIVIDUALS
PROPLANNED
Not yet set
ANNOUNCED BEFORE RELEASE
Professional individual
- Premium models
- Larger context window
- Verified Missions
- Cloud sync
- Standard sandboxes
PRO MAXPLANNED
Not yet set
ANNOUNCED BEFORE RELEASE
Heavy agent users
- Higher included usage
- Priority compute
- Advanced models
- Longer Missions
TEAMPLANNED
Not yet set
ANNOUNCED BEFORE RELEASE
Software teams
- Shared Missions
- Standards and shared review
- Private catalog
- Budgets
- Team analytics
BUSINESSPLANNED
Not yet set
ANNOUNCED BEFORE RELEASE
Scaling companies
- SSO / SCIM
- Policy and audit
- Production Twin
- Release and observability integrations
- Support
ENTERPRISEPLANNED
Not yet set
ANNOUNCED BEFORE RELEASE
Large and regulated organisations
- Custom limits
- Dedicated, VPC, self-hosted
- Residency
- SLA and technical account manager
- Security review and procurement
PLANNED USAGE METERS
Credits will be readable in dollars and typical Missions.
When the product ships, an expensive action will show the estimate, the current spend and the hard limit before it runs. Teams will choose soft or hard budget policies.
| Meter | Unit | Why it is separate |
|---|---|---|
| Agent compute | Standardised credits by model and operation | Model costs vary widely; protects margin and gives choice |
| Sandbox | vCPU / RAM / GPU minute + storage and network | Real cloud resource consumption |
| Production Twin | Environment hour + replay volume | High value, compute and data intensive |
| Evidence retention | GB-month by retention tier | Long audit retention has a durable storage cost |
| Release Control | Active environment or release volume | Platform value grows with the production footprint |
| Private runner management | Runner or cluster tier | Support, control plane and update overhead |
| Marketplace | Transaction and usage revenue share | Funds trust, billing, discovery and support |
PLANNED PACKAGING RULES
- The core editor stays genuinely useful on Free; the paywall surrounds scale, premium compute, team governance and production value.
- Included credits are understandable in dollars and typical Missions, not opaque tokens.
- The user sees an estimate, current spend and a hard limit before a compute-heavy action.
- No surprise overage by default for individuals; teams choose soft or hard budget policies.
- Annual enterprise pricing reflects deployment, support and security obligations, not only seats.
- Self-hosted is not a cheap escape from SaaS pricing; it carries a higher licence and support floor.
- Open-source maintainers and education can receive grants — adoption without destroying commercial pricing.
ALWAYS INCLUDED
Trust is not a paid feature.
Independent verification, the evidence bundle, policy-controlled release and the audit trail are part of the product, not an enterprise add-on.
Independent verification
The author of a change is never its only reviewer, on every plan.
Evidence bundle
Sealed, signed and exportable. Any mutation invalidates it.
Policy outside the model
Authorisation, budgets and forbidden actions are decided by a deterministic contour.
Local-first editing
Local editing stays available independently of the cloud.
No training on your code
Customer content is never used for training without explicit opt-in.
Export at any time
Your data and your evidence leave with you, in documented formats.
PLAN SUMMARY
At a glance.
Planned plans. Amounts are not yet determined and are not a price list.
| Plan | Price | Audience |
|---|---|---|
| Free | Not yet set announced before release | Students, evaluators, open source |
| Pro | Not yet set announced before release | Professional individual |
| Pro Max | Not yet set announced before release | Heavy agent users |
| Team | Not yet set announced before release | Software teams |
| Business | Not yet set announced before release | Scaling companies |
| Enterprise | Not yet set announced before release | Large and regulated organisations |
PRICES NOT YET DETERMINED // TO BE ANNOUNCED BEFORE THE PLANNED RELEASE ON 7 JULY 2027
COST VISIBILITY
A bill you can explain line by line.
Metering is only useful if it reconciles. Every Mission carries its own cost, every cost has a home, and a forecast states its own assumptions.
Cost of every Mission
Model, compute, storage, network and third-party components are shown for the Mission and for each of its stages.
Cost allocation
Spend is allocated by organisation, team, project and repository, and the finance export reconciles with the internal ledger and tags.
Usage forecast
Monthly usage and unit economics are forecast with the assumptions, the range and the error history attached.
QUESTIONS
Pricing questions, answered plainly.
Can I buy a plan today?
No. Astvyr has not been released: there is no public build, early access is not provided and prices are not yet determined. The planned release date is 7 July 2027. Until then you can talk to us about the product and your requirements.
Is anything on this page an offer?
No. This page describes planned packaging and planned billing rules. It is not an offer, a price commitment or a promise of availability, and it may change before release.
What happens if I go over my included usage?
The planned policy: individuals are not charged a surprise overage by default. Teams will choose a soft or hard budget policy, and a hard limit will stop an action before it spends.
Is the free plan a trial?
No. Free is planned to stay genuinely useful rather than time-limited: local analysis, a working editing loop and a small monthly Mission allowance.
Why is compute metered separately?
Because model and sandbox costs vary by orders of magnitude between operations. Metering them honestly is what keeps a flat seat price possible at all.
Is self-hosted cheaper?
No. Self-hosted will carry a higher licence and support floor, because deployment, upgrades and security obligations move to a dedicated path.
How will enterprise pricing work?
Enterprise pricing will reflect deployment, support and security obligations: dedicated or private deployment, residency, SLA, technical account management and procurement review. Not seats alone.
Do open-source maintainers pay?
Maintainers and education programmes will be able to receive grants. Adoption matters more than extracting revenue from the people who make the ecosystem work.
What is the unit you optimise for?
Cost per verified outcome: the full model, compute and support cost of one accepted Mission, by task class. Not tokens, not seats, not generated lines.
ECONOMICS
Planned: transparent economics, in dollars you can read.
After release, a compute-heavy Mission will show the estimate, the current spend and the hard limit. No opaque credits.