EnterprisePriced as a project
A change built for your organisation alone.
Some changes only make sense for one organisation. Those are built on a separate path: scoped and priced as a project, with its own timeline, and kept visibly distinct from the community queue. Enterprise work never jumps the line, and community requests never wait behind it.
How it differs from the community queue
| Community queue | Enterprise project | |
|---|---|---|
| Who it is for | Every member | One organisation |
| What gets built | Changes that fit a product’s charter and serve members generally | A change, integration or deployment that only your organisation needs |
| Who decides | The product’s steward, in public | You and the steward, under a scope you sign |
| Timeline | Decision within ten business days, weekly release window | Set in the project scope |
| Price | Included in membership | Priced as a project |
| Visibility | Public thread, build log, changelog entry naming the member | Private to your organisation, unless you choose otherwise |
| Priority | No tier moves a request up the queue | Never enters the community queue, and never delays it |
What enterprise work looks like
The same AI development team, the same verification, the same human release gate. Only the scope and the audience differ.
An integration only you use
A connection to an internal system, a data source or a provider that no other member needs.
A workflow specific to your process
A review step, a report format or a routing rule that reflects how your organisation actually works.
A private deployment
A product run for your organisation alone, with its own configuration and its own release schedule.
A change that later serves everyone
If an enterprise change turns out to fit a charter, it can be offered to the community afterwards, credited to your organisation.
What stays the same
- The charter still applies. A product will not become what its charter says it will never become, for any client.
- Verification is the same: regression, layout, accessibility and data-consistency checks, and a human release gate.
- Your keys and your data stay yours. There is no metering inside the products.
- The community queue is never delayed by enterprise work, and the scorecard does not count enterprise changes as member-sourced.
Start an enquiry
Tell us what needs to be built for your organisation alone, which product it concerns, and any timeline you have. We reply within one business day with whether it is enterprise work or a community request, and what happens next.
