Skip to the content
Vibeminter
Getting startedPublishing

Billing

Vibeminter runs on prepaid credits. There is no subscription. One balance pays for every build, every change and every publishing step on your account. Amounts are not printed on this page; the Credits page shows them to you before you pay.

Credits and your balance

You buy credits in packs on the Credits page, by card through Stripe Checkout. Your balance is shown in the left rail of the app on a computer, in the top bar on a phone and in the bar of a project. A purchase needs a verified email address.

Apple
Credits are only for work done on your account. They are not money, and Apple's own fees are separate: the Apple Developer membership is paid to Apple, not to us.

The hold and the receipt

Every change has a size class, and the size class sets the amount held. Before you send, the estimate in credits shows beside Send; that amount is held from your balance when you send, and the turn's card says how much.

When the turn ends, its card in the chat shows the receipt as a ledger: what was held, what the turn cost, how much of the hold went back to your balance and the balance now. If a turn fails, the card says so and says what was refunded. The figures are not printed on this page.

The money of one turnwhen
Held
when you send
Charged
when the turn ends
Returned
when the turn ends
Balance now
as the app shows it

Publishing steps

Scheduled
Once publishing to TestFlight is switched on for your account, preparing and sending a build to TestFlight is a priced step, with its own cost shown before you tap it. It is charged once for the run, so asking twice does not charge twice.

Limits you can set

Settings has daily spend caps for your account and for each project, and they are on by default. You can change them or turn one off, and the platform keeps its own daily ceiling that no setting lifts. A day is the UTC day.

Your records

  • Credits has the purchase history, one receipt line per payment.
  • Usage lists each project's turns, what was charged, what was refunded and the net, and downloads as a CSV file.
  • Settings has the account, data export and deletion.

Scheduled

These do not exist yet. Each one names what it waits on, and none has a date.

  • ScheduledThe written rules for when credits are returned, and the cap on what a turn can charge.
    Waits on: the final pricing decision, and proof from the ledger that each rule is enforced as written.
  • ScheduledPrices and packs on the public pricing page.
    Waits on: the pricing decision that comes from the cost pilot.
  • ScheduledThe terms of credit expiry.
    Waits on: the expiry date being carried on the credit itself, which it is not yet.
  • ScheduledA customer portal for invoices and payment methods.
    Waits on: the Stripe portal being connected to the account.