How slots work

A slot is the billing primitive in StoreFrame. Each slot is a seat on your organization's single Stripe subscription. You purchase the right to run N environments, not a per-environment price row. Slots grow as you create environments, and unused slots are dropped at renewal.

Two slot types

Project slots and Stage slots live on the same subscription. Adding a slot updates the corresponding Stripe subscription item quantity immediately, with proration applied for mid-month changes. Unused slots are dropped at renewal.

How slots are counted

Slot usage is computed from your live environments. Creating an environment increments the count; destroying it decrements it. There are no stale counters to sync.

• Project used slots environments of type production on BYOK infrastructure
• Stage used slots environments of type staging, develop, or test

Available slots = purchased slots − used slots. If you have available slots, a new environment provisions without any payment prompt.

Billing decision flow

When you create an environment, StoreFrame picks the right billing path automatically:

If you already have a subscription and a payment method on file, you never need to re-enter card details. New slots are added and charged in the background.

Prorated billing

Added slots are prorated to the day:

• Add a slot mid-month immediate charge for remaining days (minimum €1)
• Remove an environment mid-month there is no credit. A paid slot stays available until the end of the current billing period, and slots with no environment when the period ends are not billed for the next one
• First subscription immediate charge from subscribe date to end of month, then full-month billing starts on the 1st

The €1 minimum prevents micro-transactions. For example, adding a Stage slot with only 2 days remaining would be €10 × 2/31 = €0.65, rounded up to €1.

Pricing examples

Slot pages

• Project slots — €50/month, what the project slot covers
• Stage slots — €10/month, Stage environment types and common patterns