Can I start without a database?
Yes. Publish the application first and add PostgreSQL or MariaDB when the product actually needs persistent data.
Quickstart
Your first guided deployment with Zenifra
Go from repository to domain with a clear sequence: create your account, publish your application, add a database when needed, and follow logs in the console.
From repository to domain
This quickstart turns the homepage journey into a practical path: deployment, configuration, observability, and the evolution of your first project.
Step 1
Create an account
Create your account and receive initial credits to try the platform without requiring a card.
Step 2
Create a project
Continue in the console with guided configuration and documentation whenever you need technical details.
Step 3
Deploy
Continue in the console with guided configuration and documentation whenever you need technical details.
Step 4
Add a database when needed
Continue in the console with guided configuration and documentation whenever you need technical details.
Step 5
Configure a domain
Continue in the console with guided configuration and documentation whenever you need technical details.
Step 6
View logs and metrics
Continue in the console with guided configuration and documentation whenever you need technical details.
For those getting started
Common paths for validating Zenifra without turning your first deployment into an operations project.
For people getting started
Ideal for validating a first project without deciding the entire architecture on day one.
MVP with backend and database
Publish the API, add PostgreSQL or MariaDB, and follow logs while testing the product.
Teams moving away from a VPS
Replace manual scripts with a guided sequence for deployment, domain, SSL, and observability.
Your first project flow
A short sequence to go from a new account to an observable application in the console.
01
Create the account and choose a path
Start in the console and select GitHub or Docker/OCI according to the project format.
02
Configure the minimum to start
Set the HTTP port, environment variables, and a database when the application needs to persist data.
03
Publish and follow up
Validate the build, logs, deployment status, domain, and metrics before inviting users.
Decisions before opening the console
Four simple choices make deployment more predictable and prevent rework in your first project.
Deployment source
GitHub for push deployment or Docker/OCI for an already packaged image.
HTTP port
The port must match the process your application exposes inside the container.
Optional database
Add PostgreSQL or MariaDB when the product needs to store data.
Domain
Set aside the domain that will receive the mapping after the first healthy deployment.
Checklist before your first deployment
Separate the repository, variables, port, and database before opening the console. With these decisions made, your first deployment is faster and avoids early rework.
- Repository or Docker/OCI image ready for deployment
- Environment variables separated by environment
- HTTP port identified in the application
- PostgreSQL or MariaDB database defined when needed
- Domain and DNS set aside for configuration after deployment
Projects in the console
The projects view brings together applications, databases, AI, logs, and metrics so you can follow what is already running.
Create a project
The creation screen shows deployment type, port, runtime, commands, and initial settings before publishing.
After the deployment
The first deployment is only the beginning: use logs, metrics, and consumption to decide the next adjustment.
After deployment
Follow logs, metrics, consumption, and domain status to decide whether the product is ready for users.
Evolve safely
Add a database, increase instances, and adjust variables as the application matures.
Frequently asked questions
Short answers to decide your next step without leaving this page.
Do I need to configure a domain on the first deployment?
No. Validate logs and status first, then point the domain and enable the SSL flow.