This is the commercial direction we are testing, published before it is built so nobody is surprised by it later. Nothing on this page is purchasable yet, and no prices have been set.
Slotkit is not currently billed. There is no checkout, no balance, no invoice, and no refund process. When this model is accepted and implemented, it will be announced with terms before anything is charged.
Slotkit is built to reach a sufficient feature set and then move to maintenance. It will be kept secure, current, and running. It is not on a path of permanent expansion, and we would rather say so than imply otherwise.
A monthly subscription sells continued development. A product that deliberately stops adding features cannot honestly sell that, and would spend the rest of its life defending a price against a roadmap it does not intend to have.
A prepaid booking sells something a maintenance-scoped product can keep promising indefinitely: that the booking will commit, reach the calendar, and deliver its webhook. That promise gets stronger as the system settles, not weaker.
The unit is a booking that actually happened, not a seat, a connected calendar, or a monthly platform tier. A Host who takes four bookings in a quiet month would use four credits.
Uses one credit
Uses no credit
No pack size or price has been chosen.
Every workspace starts with free confirmed bookings
Granted once when the workspace is created, not refreshed monthly. Enough to finish guided setup and take real bookings before paying anything. It is counted on the server against your workspace, not in the browser.
How many has not been decided.
Individuals, consultants, and studios with irregular booking volume.
Good fit if: You want a booking page and would rather not pay a monthly fee for the months you barely use it.
Sized for about a year of one person taking a handful of bookings a week.
Small teams with several Hosts and a steady weekly rhythm.
Good fit if: You need more than one Host, clear roles, and a cost that follows bookings instead of seats.
Sized to outlast a year for a few Hosts booking regularly.
Products booking through the Public API.
Good fit if: You are integrating scheduling into your own product and do not want a monthly platform fee to clear before your first booking.
Sized for a year or more at steady API volume.
Booking above the largest pack, or need an agreement, invoicing arrangements, or a support commitment? That is a conversation, not a fourth card.
We are not planning to gate scheduling behavior behind a pack. Packs are expected to differ in how many confirmed bookings they include and what each one effectively costs — not in what the product does.
These are proposals, not settled terms. They are here because a prepaid model where the rules arrive after the purchase is not a fair one.
What is left after the proposals above. We would rather show these unanswered than answer them badly in a pricing table.
A product that plans to stop adding features owes you an answer to this question before you prepay anything, not after.
These are proposed commitments. They bind us when they are published as terms, not before.
If all you want is a page where people pick a time, there are cheaper one-time offers and free tiers, and you should use one. We are not going to argue you out of that.
Slotkit is for when the booking has to become an event inside your own system: a versioned API, signed webhooks with bounded retry, and a reliability contract we publish and can be held to.
If prepaid booking credits would or would not work for how you schedule, tell us before it is built. We are collecting early-access interest by email — there is nothing to sign up for and nothing to pay.
Email us about early access