Pricing
Plans shaped by portfolio scope
The current plan model varies by how much of your organisation it spans. Commercial pricing is not published yet.
Core
One portfolio and the team that runs it.
Not published
- The full data model, configured to your assets
- Configurable workflows, stages and approvals
- Reporting and analytics across the portfolio
- Built-in intelligence on your own context
- Up to 25 users
Scale
Several portfolios, several teams, and the reporting that spans them.
Not published
- Everything in Core
- Multiple portfolios under one model
- AI agents across your operations
- Roles, permissions and governance rules
- Integrations with the systems you keep
- Up to 100 users
Enterprise
Amkit as the system of record, across entities and regions.
Not published
- Everything in Scale
- Unlimited portfolios and users
- Single sign-on and directory sync
- Data residency and retention controls
- The developer platform and its APIs
- A named team for onboarding and support
Pricing is not published. The plan structure shown here is a working model, not a commercial offer.
Before a contract
The questions that come first
What buyers ask before pricing is agreed, answered here rather than in a call.
What decides which plan we need?
The current working model varies by how much of the organisation the platform spans. Core fits one portfolio and its team, Scale fits several of each, and Enterprise fits amkit becoming the system of record across entities and regions.
Can we start on one portfolio and widen later?
Yes, and it is the ordinary path. The model you configure on the first portfolio is the model the next ones join, so widening is a matter of bringing assets and teams into it rather than starting again.
Does the AI cost extra?
Pricing is not published yet. In the current working model, built-in intelligence is part of every plan, while agents that act across operations begin with Scale.
What happens to the systems we already run?
The ones you keep are connected; the ones amkit replaces are loaded in and retired. Which is which is decided during configuration, before anything is migrated.
Who owns the data?
You do, and it stays exportable in a form you can use elsewhere. Residency and retention are configurable on Enterprise.
Match the plan to what you actually hold
Bring your portfolio and the way your teams work, and see which working plan model fits.