Best fit for each plan
Each Zenifra plan is designed for a kind of workload. A plan that is too large costs more than it needs to; a plan that is too small makes the application slow or makes it restart for lack of memory. This section explains the focus of each plan and gives examples of applications that make sense on each one.
Choose by what you are publishing
| You want to publish | Start with | Guide |
|---|---|---|
| Static site, landing page, portfolio or prebuilt SPA | Static | HTTP plans |
| First API or dynamic site (Node.js, Python, Bun) | Basic | HTTP plans |
| Application with a database and real users | Premium | HTTP plans |
| WordPress, Metabase or internal tools | Premium Plus | HTTP plans |
| Your own AI model on a GPU | Deep Learning Basic | HTTP plans |
| Task that runs on a schedule | job-starter or job-basic | Scheduled Jobs |
| Database for learning or a prototype | db-free | Databases |
| Production database | db-starter or db-basic | Databases |
| Session or query cache | cache-starter | Cache and Queues |
| Task queue for workers | queue-starter or queue-basic | Cache and Queues |
Three rules for choosing
- Start with the smallest plan that fits the application. On hourly projects, you can change the plan later in Edit project, except to or from the Free plan.
- Memory is the hardest limit. Too little CPU makes the application slow; too little memory makes it restart. If the application needs a language that keeps running all the time (Node.js, Python, PHP, Java), do not choose Static.
- More traffic does not always need a bigger plan. On paid HTTP projects, auto-scaling adds instances when traffic grows. Move up a plan when a single instance cannot keep up.
In this section
- Which HTTP plan to choose: Free, Static, Basic, Premium, Premium Plus, Business and Deep Learning.
- Which plan to choose for Scheduled Jobs:
job-starter,job-basicandjob-premium. - Which database plan to choose: PostgreSQL, MariaDB, Valkey Key-Value and Analytics.
- Which plan to choose for Cache and Queues.
Current prices appear in the console when you create each project and in the zenifra plans command.
Last updated on
Platform concepts
Understand organizations, projects, plans, payment models, instances, deployment sources, domains, and API keys before you start using Zenifra.
Which HTTP plan to choose for your application
What each Zenifra HTTP plan is for, from Free to Deep Learning, with examples of applications that run well on each one and signs that it is time to switch.