# How slots work

Source: https://www.storeframe.io/docs/billing/slot-model

Slots are the billing primitive in StoreFrame — each slot is a seat on your organization's subscription.

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.

![Monthly Billing card](https://www.storeframe.io/assets/docs/billing/slot-model/monthly-billing-card.jpeg)

## Two slot types

| Slot type    | Price     | What it covers                            |
| ------------ | --------- | ----------------------------------------- |
| Project slot | €50/month | One production environment                |
| Stage slot   | €10/month | One staging, develop, or test environment |

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:

| Your situation                    | What happens                                                            |
| --------------------------------- | ----------------------------------------------------------------------- |
| Available slot exists             | Slot used immediately, provisioning starts — no payment prompt          |
| Subscription active, no free slot | New slot added with immediate prorated charge, provisioning starts      |
| No subscription                   | Stripe Checkout opens — enter payment details, then provisioning starts |

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

| Configuration         | Monthly cost |
| --------------------- | ------------ |
| 1 Project slot        | €50          |
| 1 Project + 1 Stage   | €60          |
| 1 Project + 2 Stages  | €70          |
| 3 Projects, no Stages | €150         |
| 3 Projects + 4 Stages | €190         |

## Slot pages

* [Project slots](/docs/billing/slot-model/projects) — €50/month, what the project slot covers
* [Stage slots](/docs/billing/slot-model/stages) — €10/month, Stage environment types and common patterns
