Payment Models on the Zenifra Platform

On Zenifra, HTTP projects, databases, and managed services can operate under three billing modes:

Hourly billing
Monthly billing
Yearly billing

Each model fits a different usage profile and changes how cost, project stop behavior, and contract changes work. Scheduled Jobs have their own billing, per execution minute (see below).

Hourly Billing

Hourly billing is the most flexible model on the platform.

How it works

the amount is proportional to running time: the plan's hourly price × running hours (including fractions of an hour) × number of instances
a stopped project does not generate compute charges; additional persistent storage is still billed separately
if the organization does not have enough credit, the platform tries to use the saved card as automatic fallback

Examples

If a project with 1 instance runs for 30 minutes, the billed value will be the equivalent of half an hour of the plan.
If a project with 2 instances runs for 3 hours, the billed value will be the equivalent of 6 hours of the plan.

When to use it

testing and development
prototypes and POCs
temporary projects
workloads that do not need to stay active 24/7

Monthly Billing

The monthly model is recommended for projects that need predictable cost during the whole contracted period.

How it works

the project stays reserved during the contracted period
the final contract value does not change even if the project is stopped temporarily
stopping the project can make it inaccessible, but it does not reduce the contracted billing amount

When to use it

production APIs
24/7 applications
institutional websites
services that need predictable cost

Yearly Billing

The yearly model follows the same contract logic as the monthly model, focusing on long-term projects.

How it works

billing follows the commercial conditions of the current offer
the project remains reserved during the whole contract
stopping the project does not reduce the final amount billed during the contracted period
automatic renewal is optional

When to use it

long-term projects
critical systems
workloads that require operational and financial predictability

Scheduled Jobs are billed per execution minute, rounded up, with a minimum of 1 minute per execution. Each execution can run for up to 60 minutes; after that it is stopped as Timed out. See the plans in Scheduled Jobs.

Organization Credit

Credit belongs to the organization, in BRL, and is shared across different types of charges, including:

HTTP projects
databases and managed services
scheduled Jobs
persistent storage
AI usage
other platform charges

When there is available credit, it is used first.

Non-refundable credit

Credit added by PIX or boleto can be used only on the platform: it is non-refundable, cannot be converted into cash or transferred to third parties, without prejudice to the rights the law grants to consumers. Promotional credit has no monetary value and follows the rules of the respective campaign. Remaining credit is also not refunded when the account is deleted: it is closed together with the account.

Insufficient credit

When the organization runs out of credit:

the platform tries to charge the saved card
if there is no card or the charge fails, the amount is recorded as an outstanding amount (negative balance)
if outstanding amounts persist across consecutive billing cycles, the organization is blocked: you cannot create or resume projects until the balance is settled, and running projects may be paused automatically

This rule applies to postpaid platform charges. AI is prepaid: when no usable credit remains, new calls are blocked and the card is not used as a fallback to increase AI usage.

This pending debt can be tracked and settled in Billing, in the console, by adding credit with PIX or boleto. After settling, resume paused projects manually.

Payment Methods

The accepted payment methods are:

Pix
bank slip
credit card in BRL

Minimum amounts

Pix: from R$5,00 to R$5.000,00
bank slip: from R$30,00 to R$49.999,99

Credit card

The credit card works as an automatic billing fallback when the organization credit is not enough. It is not used to add credit.

AI and token billing

Zenifra's AI offering uses token billing and shares the same account credit.

prices (per million tokens or, for image models, per image) and available models can be checked in AI models, in the console
usage is consolidated in the organization billing cycle
only usable credit authorizes new AI calls
without credit, new calls are blocked
each key's configured limit is an additional restriction and does not increase the organization's credit
promotional credits, when granted, can also be used with AI

New users receive R$30.00 in promotional credit while the promotion is available.

For details about the AI offering, see AI on Zenifra.

How to choose the ideal model

Model	Best use
Hourly	Testing, development, intermittent usage
Monthly	Production projects with predictable cost
Yearly	Long-term projects and continuous contracts

Next steps

FAQ

Can I change a project's plan?

Hourly projects can change plans at any time, except to free plans. On monthly or yearly contracts, plan changes are not allowed during the contract; you can turn off automatic renewal in the project edit page so the contract is not renewed at the end of the period.

What happens if I stop a monthly project?

The project may become unreachable, but the contract value does not change. To pay only for running time, use the hourly model.

Can credit be refunded?

No. Credit can only be used on the platform, as described in the non-refundable credit section above.

Questions about payments? Email: [email protected]

On this page