Fliplet credits are the unit of measurement for everything you do in your workspace. Building projects with AI, publishing them, storing files, sending notifications, querying data, and serving them to end-users all draw on the same credit balance. Your plan includes a monthly credit allowance, and credits reset at the start of each billing cycle.
This article explains how credits work, what they’re spent on, and how to read your usage. For what to do when you run out, see What to do when you reach your credit limit. For billing actions, see Manage billing, top-ups, and your subscription.
Contents
How credits work
Every plan comes with a monthly credit allowance. Each action debits a small number of credits from your allowance. Examples include generating a project with AI, publishing to the App Store, sending an email, and an end-user opening a published project.
Usage is tracked per organization, not per project. If you have several projects in the same workspace, they all draw from the same monthly balance.
You can keep an eye on usage above the chat input while building, and on the Manage organization > Billing page for a full breakdown by activity and by project.
What consumes credits
Credits are spent across five broad categories: building projects with AI, owning and publishing projects, storing files, end-user activity in published projects, and data and communications sent from your projects.
AI generation is by far the most variable cost. It scales with prompt size, output length, and the model being used. Long iterative sessions on the same project cost less per message than short isolated prompts because the AI reuses cached context.
The examples below give a feel for typical costs in real scenarios. Your exact spend always shows on the Billing page.
Typical scenarios
| Scenario | Approximate cost |
|---|---|
| Building a simple project from scratch (a contact form, a hero page, a short list-and-detail screen) | Around 30 to 100 credits, depending on how many iterations it takes |
| Building a feature-rich project over several sessions (multiple screens, authentication, custom logic) | Several hundred to a few thousand credits |
| Keeping one project in your workspace | 0.5 credits per project per month |
| Publishing one project to the web | 2 credits per month, per project |
| Publishing one project to both iOS and Android | 6 credits per month, per project (3 each). Add 2 more credits per platform for private distribution (MDM or ABM). |
| Storing 1 GB of media files in a project | 4 credits per GB per month |
| A published project used by 100 unique end-users in a month | 25 credits (0.25 per unique end-user) |
| A published project used by 1,000 unique end-users in a month | 250 credits for the end-user opens, plus what the project’s own data activity adds (typically a few hundred more for a moderately active project) |
| Sending an email to 1,000 recipients | 100 credits (0.1 per recipient) |
| Sending 100 SMS messages | 50 credits (0.5 per message) |
| An automation that runs once an hour for a full month | 108 credits (0.15 per run × 24 × 30) |
Cost categories at a glance
- AI generation in the builder. Variable. Scales with prompt and response size and model choice. Usually the dominant cost while you’re actively building. Includes everything the AI does on your behalf: generating text, fetching pages from the web (0.05 per fetch), saving an image to your media library (0.1 per save), inspecting a page with a real browser (0.2 per inspection), generating images (varies by size, quality, and model), transcribing audio, and embeddings for search.
- Owning and publishing projects. A small monthly charge per project you keep in your workspace (0.5), plus a small monthly charge per channel you publish to (2 for web, 3 each for iOS and Android, 2 per platform for private MDM/ABM distribution). Republishing within the same month is free.
- File storage. 4 credits per GB stored in your media library per month. The charge is calculated against your total V3 project storage once per cycle. If you delete a file partway through the cycle, the freed space is refunded against that cycle’s running total.
- End-user activity. A small charge for each unique end-user who opens a published project each month (0.25), plus tiny amounts per data query or write the project makes (0.01 per read, 0.05 per write). In-project AI (such as a chat assistant inside a published project) bills the same as Studio AI and uses the same model tiers.
- Communications. Email (0.1 each), SMS (0.5 each), and push notifications (0.02 each) charge per message sent. SMS is the most expensive because of carrier costs. Push notifications are the cheapest.
- Other. Maps API calls (0.08 each), automation runs (0.15 each), and a small per-row storage charge for data sources used in your projects (0.005 per record per cycle).
Internally, Fliplet groups these into two pools. A build pool covers actions you take inside the builder (AI generation, publishing, sending emails or SMS from Studio). A run pool covers end-user activity in published projects (opens, data reads and writes, in-project AI, server-side automations triggered from a live project). Both pools draw from the same monthly allowance, and you can see the split on the Billing page.
For the exact per-action cost of any line on your bill, see the Breakdown tab on the Billing page. Each row shows the activity, the cost, and the project it came from.
Plans and allowances
Each plan gives you a monthly allowance and a set of workspace features. Paid plans give more credits, more team seats, and a 10% grace buffer above 100% on end-user activity in published projects, so a single busy day doesn’t take live projects offline straight away. (Free has no grace buffer. See What to do when you reach your credit limit for how that buffer works.)
New pricing is coming soon
Right now, Fliplet’s brand new AI builder is available on a free plan for building, prototyping, and validating ideas.
Viewing your usage
You can check your credit usage in two places:
- Above the chat input in the Fliplet Studio builder. Shows the percentage of your monthly allowance used so far (for example, 72% of credits used). The row is visible throughout the cycle to everyone in the workspace, admin or standard user. At 70%, 80%, and 90% the row shifts to a warning state to flag the threshold; at 100% it shows Credit allowance reached for this period.
- Manage organization > Billing. Shows your current plan, monthly allowance, total used, top-up balance, next reset date, and a breakdown by activity and by project. Values are shown to two decimal places, so a balance of 999.50 displays as 999.50 (not rounded up to 1,000).
Cycle resets
Credits reset once a month. The exact reset date for your organization is always shown on the Billing page on the plan tile.
You can expect the reset to fall on roughly the same day each month. The exact date depends on when your organization’s cycle started, so always check the Billing page as the source of truth.
At each cycle reset, recurring charges are applied for the new cycle:
- Projects in your workspace are recharged (0.5 credits each).
- Published projects are recharged per channel (2 for web, 3 each for iOS and Android, plus 2 per platform for private distribution).
- File storage is billed against your total media storage at the start of the cycle (4 credits per GB).
- Data source storage is billed against the total number of records (0.005 per record).
These show on the Billing page on the day of the reset and are included in the new cycle’s running total.
Unused monthly credits do not roll over to the next cycle. Top-up credits behave differently. They sit alongside your monthly allowance and stay available until they are spent.
On annual paid plans, the plan tile shows both dates. Resets is when your monthly credits refill. Renews is when your annual subscription renews.
Top-ups
If you finish your monthly credits before the cycle resets, you can buy a top-up to keep working without changing plans. Top-ups are available on every paid plan and are charged at a flat rate of $0.01 per credit (in USD). This is a higher per-credit rate than the monthly subscription plans, so top-ups are best used for one-off bursts; sustained higher usage is usually cheaper on a higher plan.
Top-up credits are spent only after your monthly allowance is exhausted and they don’t expire. Unused top-up credits carry over from cycle to cycle until you use them.
To buy a top-up, see Manage billing, top-ups, and your subscription.