How does founder pricing work?
Customers enter in numbered cohorts. Each cohort has a slot count and a monthly price. When a cohort fills up it closes and the next one opens at a higher price. Your price is the price of the cohort you entered.
Pricing
Early customers pay less. And keep paying less.
Venkai's price steps up as customers arrive — not as time passes. The rung you join is the rung you keep. Every figure on this page is read from the ledger at the moment the page is served to you.
Current cohort
Founding customers
€250
excl. VAT / month / organisation
0of10
founder slots claimed — 10 left
Next cohort
Founding customers II
€300
Applies once the current cohort is full.
Your price is locked the moment you enter, together with the pricing version and the cohort id. A later increase does not change it.
Pilot — 3 weeks, one organisation — €4,500
Flat in every cohort. It buys a measurement on your repository, not a subscription.
Pricing version 2026-08-v1
The ladder
What each rung costs, and from which customer.
A cohort closes when it reaches its customer count, not on a date. A closed rung keeps the price it was sold at.
| Cohort | Customers | Monthly price | State |
|---|---|---|---|
| Founding customers | 1–10 (0/10) | €250 / month | Open |
| Founding customers II | 11–25 (0/15) | €300 / month | Upcoming |
| Early customers | 26–50 (0/25) | €350 / month | Upcoming |
| Standard | 51 and beyond | €400 / month | Upcoming |
History
Every price change, dated.
Written once, never edited. It is what lets us show that a price went up instead of asserting it.
| 1 Sept 2026 | Cohort opened | founder-1 | €250 |
Trust
How founder pricing works
- 01Why it is cheaper at the startEarly customers buy a product with less usage behind it, fewer integrations and a single person answering. The price reflects that risk — it rewards taking one, not deciding fast.
- 02How many slots existThe number above is how many rows the cohort can hold in the ledger. It is not a page decision: the database refuses the slot past it, and two simultaneous signups cannot take the same one.
- 03When a cohort closesWhen it reaches its customer count. It can also be closed by hand — and then the reason is written into the ledger next to the date.
- 04How the price movesThe next cohort opens at the next rung. The price rises for new entrants only, and the write that opens it is timestamped.
- 05How your price is lockedOn entry, your row stores the price in cents, the currency, the period and the pricing version. Nothing in the code rewrites that amount: the lock is the absence of that write path, not a commercial promise.
- 06How we avoid fake countersThe counter is a COUNT over real rows. An abandoned checkout gives its slot back after 30 minutes; a cancellation does not give it back, so the number of remaining slots never quietly goes up again.
What changes
Between two rungs, only the price changes.
The product is identical in every cohort: same edit engine, same limits, same support. A more expensive cohort unlocks nothing extra, and a founder cohort takes nothing away.
What a founding customer gets on top is short, deliberately: the locked price, a direct channel to the person writing the product, and real influence over roadmap order. Nothing else is promised here until something else is delivered.
Questions
When does the price increase?
When the current cohort reaches its customer count. Not on a date, not at the end of a countdown. The remaining-slots figure at the top of this page is what triggers the increase.
Do founding customers keep their price?
Yes. The price is stored on the customer's row when they enter, along with their pricing version. A price increase opens a new cohort; it does not touch existing rows. Cancelling and coming back restores the original price.
How many founding spots are available?
The counter at the top of this page. It counts slots actually held: active customers, cancelled customers (who keep their slot and their price) and reservations under 30 minutes old. It is never reset.
The price locks when the pilot is signed.
Describe your multi-agent workflow and where an edit breaks something. We answer with a pilot scope and the cohort you would enter — or with the reason Venkai is not the right piece.
Describe your workflow