Published on
Hourly, monthly, or yearly: which billing pays off for your project?
On Zenifra, hourly billing pays off while the project runs fewer hours than the plan’s break-even point, which ranges from 545 to 598 hours a month on paid HTTP plans; above that, monthly is cheaper, and yearly costs about the same as 11 months. Everything is billed in Brazilian reais from the organization credit, added by PIX or boleto, with the card as a backup and no international purchase IOF.
Which billing mode to choose
Use hourly billing while the project runs fewer hours in the month than the plan’s break-even point, which on paid HTTP plans ranges from 545 to 598 hours; above that, monthly is cheaper, and yearly costs about the same as 11 monthly payments. Tests, prototypes, and projects that sleep at night go hourly; production running 24 hours a day goes monthly or yearly.
The mode is chosen per project at creation, in the payment type field of the Console, and applies to HTTP applications, PostgreSQL, MariaDB, ClickHouse, and Valkey services (Key-Value, Cache, and Queue). Scheduled Jobs have their own rule, per minute of execution, and AI is billed per token. So you can have an API on a yearly contract, a database on a monthly contract, and a test environment billed hourly in the same organization, all paid from the same credit.
The difference between the modes is not just price. With hourly billing, stopping the project brings compute cost to zero, and you can change the plan, change instances, and increase storage at any time. On monthly and yearly contracts, the project is reserved at a fixed price: stopping it does not lower the bill, and plan, instances, and storage are locked until the end of the period. The right choice depends on how long the project runs and how much it is still going to change.
This guide uses the exact prices from Zenifra’s public catalog checked on 11/06/2026, in Brazilian cents (590 means R$ 5.90). The break-even and yearly discount math is written out so you can redo it with your own plan.
How hourly billing works
At cycle close, Zenifra adds up the project’s running hours, multiplies them by the number of instances, and rounds the total up to the next full hour. The amount billed is the plan’s hourly price times that total. Rounding happens once, on the cycle total, not every time the project starts: 10 minutes in the month count as 1 hour, and 7 hours and 1 minute count as 8 hours.
A stopped project has 0 instances and generates no compute charges. When resumed, it comes back with the number of instances it had when stopped, and billing starts again. Additional persistent storage is different: it is billed in proportion to time, without rounding, and keeps being billed while the project is stopped, because the data is still stored. The hourly storage price is the monthly price per GB divided by 720.
If you change plans during the cycle, each plan’s hours are billed at its price, and whatever is left to complete the full hour is billed at the plan’s price at cycle close. Hourly billing also lets you change instances and increase storage while running; storage can only grow, never shrink. Elastic auto-scaling replicas are billed per hour of use.
- 1 instance running 30 minutes in the cycle: billed as 1 hour of the plan.
- 2 instances running 3 hours: billed as 6 hours of the plan.
- 2 instances running 1 hour and 15 minutes: the total is 2h30, billed as 3 hours of the plan.
- A 20-hour test on the Static plan: 20 × R$ 0.01 = R$ 0.20, the example on the pricing page.
Charges are processed once a month, on the date shown under Next processing date on the Console’s Billing page. On that date, the period’s usage is debited from the organization credit.
How monthly and yearly contracts work
On a monthly contract, the project is reserved for the contracted period and the final amount does not change if you stop the project temporarily. Stopping may make the application unreachable, but it does not lower the charge. Plan, instances, and storage stay fixed during the contract, and storage above the included amount becomes part of the contract, billed at creation at the monthly price per GB.
The yearly contract follows the same logic for long-term projects: the project stays reserved for the whole year, stopping does not lower the amount, and storage above the included amount is billed at creation at 12 times the monthly price per GB. Automatic renewal is optional; it starts on when you move a project to a contract and can be turned off later, in project editing, by an organization owner.
Trading flexibility for predictability is the core decision. With a contract, you know exactly what you will pay each month, even with variable traffic, but you cannot move up a plan mid-period: if the application grows, the plan change waits until the contract ends. The practical recommendation is to put what is already stable on a contract (the production API, the main database) and keep hourly what is still changing size (test environments, new services, seasonal workloads).
HTTP application prices and the break-even point
The table lists the HTTP application plans from the public catalog (https://api.zenifra.com/v1/project/plans) on 11/06/2026, with each instance’s hourly, monthly, and yearly price. The last column is the break-even point: the monthly price divided by the hourly price, that is, how many instance hours in the cycle cost the same as one monthly payment.
The math is direct. On Static, R$ 5.90 ÷ R$ 0.01 = 590 hours: up to 590 hours in the month, hourly costs the same or less; above that, monthly pays off. On Basic, R$ 29.90 ÷ R$ 0.05 = 598 hours. On Premium, R$ 62.90 ÷ R$ 0.11 = 571.8 hours, so 571 hours are still cheaper hourly (571 × R$ 0.11 = R$ 62.81) and 572 already exceed monthly (R$ 62.92). On Premium Plus, R$ 119.90 ÷ R$ 0.22 = exactly 545 hours.
To compare with a full month running: a 30-day month has 720 hours and a 31-day month has 744. A Basic instance running 720 hours billed hourly costs 720 × R$ 0.05 = R$ 36.00, against R$ 29.90 monthly; at 744 hours, R$ 37.20. Since every paid HTTP plan breaks even between 545 and 598 hours, any application that stays up all month is cheaper on a contract. In calendar days, the break-even sits between 22.7 and 24.9 days running 24 hours.
Remember these are instance hours. Two instances running 300 hours add up to 600 instance hours, already past Basic’s break-even.
| Plan (resources per instance) | Hourly | Monthly | Yearly | Break-even (monthly ÷ hourly) |
|---|---|---|---|---|
| Static (0.1 vCPU, 128 MB) | R$ 0.01 | R$ 5.90 | R$ 64.90 | 590 h |
| Basic (0.5 vCPU, 512 MB) | R$ 0.05 | R$ 29.90 | R$ 328.90 | 598 h |
| Premium (1 vCPU, 1 GB) | R$ 0.11 | R$ 62.90 | R$ 657.90 | 571.8 h |
| Premium Plus (2 vCPU, 2 GB) | R$ 0.22 | R$ 119.90 | R$ 1,315.90 | 545 h |
| Business (8 vCPU, 8 GB) | R$ 0.86 | R$ 479.90 | R$ 5,263.90 | 558.0 h |
| Deep Learning Basic (4 vCPU, 4 GB, RTX 3060 12 GB) | R$ 0.94 | R$ 519.90 | R$ 5,725.90 | 553.1 h |
| Deep Learning Premium (8 vCPU, 8 GB, RTX 4090 24 GB) | R$ 2.99 | R$ 1,654.90 | R$ 18,199.90 | 553.5 h |
Managed database prices and the break-even point
Managed databases use the same three modes. The table uses the catalog at https://api.zenifra.com/v1/project/database/plans on 11/06/2026, with prices per instance. Storage is billed separately, per GB on each instance; for PostgreSQL, the site FAQ states R$ 0.20 per GB of disk per month.
Databases break even later than applications. On db-starter, R$ 11.90 ÷ R$ 0.018 = 661.1 hours; on db-basic, R$ 49.90 ÷ R$ 0.076 = 656.6 hours; on db-enterprise, R$ 489.00 ÷ R$ 0.75 = exactly 652 hours. The odd case is db-premium: R$ 129.90 ÷ R$ 0.18 = 721.7 hours. In a 720-hour cycle, hourly costs 720 × R$ 0.18 = R$ 129.60, R$ 0.30 less than monthly; in a 744-hour cycle, it costs R$ 133.92, and monthly becomes worth it.
One reading detail: the pricing page shows hourly prices with two decimals (for example, R$ 0.02/h on db-starter), but the catalog and the database plans documentation show the exact value, R$ 0.018 per hour, which is what billing uses. MariaDB always runs 3 instances (one primary and two replicas), so the plan price is multiplied by 3. PostgreSQL scales from 1 to 6 instances, and on a monthly or yearly contract the instance count is fixed.
| Plan (per instance) | Hourly | Monthly | Yearly | Break-even (monthly ÷ hourly) |
|---|---|---|---|---|
| db-starter (0.3 vCPU, 256 MB) | R$ 0.018 | R$ 11.90 | R$ 130.90 | 661.1 h |
| db-basic (1 vCPU, 1 GB) | R$ 0.076 | R$ 49.90 | R$ 548.90 | 656.6 h |
| db-premium (2 vCPU, 2 GB) | R$ 0.18 | R$ 129.90 | R$ 1,428.90 | 721.7 h |
| db-enterprise (8 vCPU, 8 GB) | R$ 0.75 | R$ 489.00 | R$ 5,388.90 | 652 h |
How much a yearly contract saves, with the math
The yearly discount is the difference between 12 monthly payments and the yearly price, divided by the 12 monthly payments. On Basic: 12 × R$ 29.90 = R$ 358.80; yearly costs R$ 328.90; the saving is R$ 358.80 − R$ 328.90 = R$ 29.90, or R$ 29.90 ÷ R$ 358.80 = 8.33%. In other words, Basic yearly costs 11 monthly payments: you pay for 11 months and use 12.
The same math holds for most plans: Static, Basic, db-starter, db-basic, and db-premium get exactly one monthly payment off (8.33%). Premium is the exception on the high side: 12 × R$ 62.90 = R$ 754.80, against R$ 657.90 yearly, a saving of R$ 96.90, or 12.84%, the equivalent of 1.54 monthly payments. Premium Plus (8.54%), Business (8.59%), and Deep Learning Premium (8.35%) sit slightly above one monthly payment; Deep Learning Basic (8.22%) and db-enterprise (8.16%), slightly below.
The discount only exists if the project stays up all year on the same plan. Since yearly locks plan, instances, and storage for 12 months, it makes sense for what is already sized. If the application may need a bigger plan in the coming months, monthly gives the same predictability with a smaller commitment: at the end of each month, without renewal, you choose again.
| Plan | 12 × monthly | Yearly | Yearly saving | Discount |
|---|---|---|---|---|
| Static | R$ 70.80 | R$ 64.90 | R$ 5.90 | 8.33% |
| Basic | R$ 358.80 | R$ 328.90 | R$ 29.90 | 8.33% |
| Premium | R$ 754.80 | R$ 657.90 | R$ 96.90 | 12.84% |
| Premium Plus | R$ 1,438.80 | R$ 1,315.90 | R$ 122.90 | 8.54% |
| Business | R$ 5,758.80 | R$ 5,263.90 | R$ 494.90 | 8.59% |
| db-starter | R$ 142.80 | R$ 130.90 | R$ 11.90 | 8.33% |
| db-basic | R$ 598.80 | R$ 548.90 | R$ 49.90 | 8.33% |
| db-premium | R$ 1,558.80 | R$ 1,428.90 | R$ 129.90 | 8.33% |
| db-enterprise | R$ 5,868.00 | R$ 5,388.90 | R$ 479.10 | 8.16% |
Three profiles with numbers: weekend, MVP, and 24/7 production
Weekend project. A Node.js API on Basic that you only run on Saturdays and Sundays, 8 hours a day, across 4 weekends: 8 × 8 = 64 hours. Hourly, 64 × R$ 0.05 = R$ 3.20 for the month; PostgreSQL on db-starter, running the same hours, adds 64 × R$ 0.018 = R$ 1.152, plus R$ 0.20 for 1 GB of disk, a total of R$ 4.552. Monthly, the same Basic with db-starter would cost R$ 42.00. The risk in this profile is leaving the project running: 720 hours of Basic in a 30-day month cost R$ 36.00, more than the R$ 29.90 monthly plan. Stop the project when you are done.
MVP under validation. An application on Basic and a PostgreSQL db-starter with 5 GB of disk, both up all month. Monthly: R$ 29.90 + R$ 11.90 + 5 × R$ 0.20 = R$ 42.80. Hourly, in a 720-hour month: 720 × R$ 0.05 = R$ 36.00, plus 720 × R$ 0.018 = R$ 12.96, plus R$ 1.00 of disk, for a total of R$ 49.96. Monthly saves R$ 7.16 and still lets you rethink the plan every month, which fits a phase when the application’s size changes fast.
24/7 production. Two Premium instances and a PostgreSQL db-basic with 20 GB, up all year. Monthly: 2 × R$ 62.90 + R$ 49.90 + 20 × R$ 0.20 = R$ 179.70 a month, or R$ 2,156.40 over 12 months. Yearly: 2 × R$ 657.90 + R$ 548.90 + 12 × R$ 4.00 of disk = R$ 1,912.70. The saving is R$ 243.70 a year (11.30%). Hourly, in a 720-hour month, the same setup would cost 2 × R$ 79.20 + R$ 54.72 + R$ 4.00 = R$ 217.12.
| Profile | Hourly | Monthly | Yearly (per year) | Best option |
|---|---|---|---|---|
| Weekend: Basic + db-starter 1 GB, 64 h | R$ 4.552 | R$ 42.00 | R$ 462.20 | Hourly |
| MVP: Basic + db-starter 5 GB, 720 h | R$ 49.96 | R$ 42.80 | R$ 471.80 | Monthly (plan still changing) |
| Production: 2× Premium + db-basic 20 GB | R$ 217.12 (720 h) | R$ 179.70 | R$ 1,912.70 | Yearly |
The MVP on yearly adds up to R$ 328.90 + R$ 130.90 + 12 × R$ 1.00 of disk = R$ 471.80, against R$ 513.60 in 12 monthly payments. The application-plus-database scenarios open ready-made in the calculator, which also estimates previews and AI.
How to pay: organization credit, PIX, boleto, and card, with no IOF
Credit lives in the organization, in Brazilian reais, and is shared across HTTP projects, databases and managed services, scheduled Jobs, persistent storage, and AI. You add credit on the Console’s Billing page by PIX, from R$ 5.00 to R$ 5,000.00, confirmed within a few minutes, or by boleto (bank slip), from R$ 30.00 to R$ 49,999.99, which is due in 2 days and may take up to 1 business day to clear. Credit only comes in through PIX or boleto.
The credit card in BRL is not used to add credit: it is the automatic fallback for postpaid charges. On the processing date, application and database usage comes out of the credit; if it is not enough, the platform tries the card; with no card or a declined charge, the amount stays outstanding as a negative balance. If outstanding amounts persist for consecutive cycles, the organization is blocked from creating or resuming projects and upgrading plans, and running projects may be paused until it is settled. AI is prepaid: without usable credit, new calls are blocked, and the card does not extend that usage.
Because the charge is issued in reais, there is no currency exchange and no international purchase IOF. For comparison, a US$ 25 monthly plan paid with a Brazilian card, converted at the PTAX selling rate of 11/05/2026 (R$ 5.4621), becomes 25 × R$ 5.4621 = R$ 136.5525, plus 3.5% IOF (R$ 4.7793), for a total of R$ 141.3318, before the issuing bank’s spread. The 3.5% rate for international card purchases is set by Decree 6,306/2007, article 15-B, item VII, as worded by Decree 12,499/2025.
Credit added by PIX or boleto is for use on the platform only: it is non-refundable, cannot be converted into cash or transferred, without prejudice to consumer rights under the law, and it ends with the account.
How to switch billing modes
From hourly to a contract, an organization owner makes the switch in the Console. The contract starts immediately; the plan’s monthly or yearly price is charged at the next processing date and then every month or year. Hours used before the switch are still billed hourly at cycle close. Plan, instances, and storage become fixed, and automatic renewal starts on.
The reverse, from a contract to hourly, is not allowed during the contract. What you control is renewal: the owner can turn off automatic renewal in project editing so the contract does not renew at the end of the period. Plan changes follow the mode too: hourly, the plan can change at any time; on a contract, it cannot change until the period ends.
- Open the project or database editing screen in the Console.
- In the Contract card, choose Monthly contract or Yearly contract.
- Click Switch to contract and confirm.
- To avoid renewing at the end of the period, turn off automatic renewal on the same screen.
Does stopping the project lower the bill on a monthly contract?
No. On a monthly or yearly contract, the project is reserved and the contract amount does not change if you stop it; the application may become unreachable, but the charge stays the same.
To pay only for running time, use hourly billing: a stopped project has 0 instances and generates no compute charges, and only additional persistent storage keeps being billed.
What happens if the organization runs out of credit?
For postpaid charges, the platform tries the saved card; if there is no card or the charge fails, the amount is recorded as outstanding, a negative balance you settle by adding credit through PIX or boleto.
If outstanding amounts persist for consecutive billing cycles, the organization is blocked: you cannot create or resume projects, move up a plan, or increase instances or storage, and running projects may be paused. After settling, resume paused projects manually.
Can I add credit with a credit card?
No. Credit is only added by PIX (from R$ 5.00 to R$ 5,000.00) or boleto (from R$ 30.00 to R$ 49,999.99). The credit card in BRL works as an automatic backup for postpaid charges when credit is not enough.
The organization has a single saved card; replacing it switches the card for upcoming charges, and if the new one is declined, the previous card stays in place.
Do scheduled Jobs and AI follow the same rules?
Not exactly. Scheduled Jobs are billed per minute of execution, rounded up, with a minimum of 1 minute per run, and each run can last up to 60 minutes. In the 11/06/2026 catalog, job-starter costs 0.01666666 cents per minute, that is, R$ 0.0001666666 per minute.
AI is billed per token, is prepaid, and uses the same organization credit: only usable credit authorizes new calls, and each key’s limit is an additional restriction. Prices per million tokens are listed under AI models in the Console.
Does Zenifra billing include IOF?
There is no international purchase IOF, because the charge is issued in Brazilian reais and involves no currency exchange. The 3.5% IOF applies when you pay for a service billed in a foreign currency with a card issued in Brazil.
Beyond the tax, a dollar invoice moves with the exchange rate on the processing day and the bank’s spread. In reais, the amount billed is the catalog price, the same from one month to the next as long as the plan does not change.