Can I use a private registry?
Yes. Configure registry credentials before deployment so Zenifra can retrieve the image.
Technical deployment
Docker/OCI for production-ready services
Publish APIs, backends, and internal tools from a public image or private registry, with port, variables, instances, and domain in the console.
For packaged services
Use Zenifra as the operating layer between your OCI image and the online product: configuration, publishing, logs, and scaling without managing a VPS.
Provide a public image or private registry
Configure it in the console and follow logs to verify that the application started on the expected port.
Set the application port
Configure it in the console and follow logs to verify that the application started on the expected port.
Configure environment variables
Configure it in the console and follow logs to verify that the application started on the expected port.
Choose a plan and number of instances
Configure it in the console and follow logs to verify that the application started on the expected port.
Follow logs and connect a custom domain
Configure it in the console and follow logs to verify that the application started on the expected port.
When to use Docker/OCI
The path for applications that already have an image and need an operating layer in Brazil.
When to use Docker/OCI
Use it when the application is already packaged in an image and you want runtime control without operating a VPS.
Internal tools
Run dashboards, automations, and internal APIs with domain, port, and variables in the console.
SaaS backend
Publish services that need databases, storage, logs, and instance-based scaling.
Image and registry
The flow starts with the right image and continues through runtime, storage, domain, and observability.
01
Provide the image and registry
The image and registry may be public or private, as long as credentials are configured.
02
Configure the runtime
Set the port, variables, storage, and number of instances before publishing.
03
Validate production
Follow logs, domain, and service health before opening real traffic.
Runtime configuration
Define the pieces that determine how the image starts and how it is observed in production.
Image and registry
Separate the OCI image and credentials if the registry is private.
Exposed port
The configured port must match the port the process listens on inside the image.
Storage
Enable persistence when the application writes files or local state.
Instances
Start small and increase capacity as logs and metrics indicate a need.
Production checklist
Review the image, port, variables, and storage before publishing. This flow is ideal for APIs, HTTP workers, and internal tools that already follow a Docker/OCI pattern.
- Public OCI image or private-registry credential available
- Application port configured for the process
- Persistent storage enabled when the application writes data
- Sensitive variables configured in the console
- Custom domain pointed after the first healthy deployment
Docker/OCI deployment
The configuration should make the image, registry, port, variables, and instances visible before the first deployment.
n8n example with an OCI image
image=docker.io/n8nio/n8n:2.5.2
port=5678
N8N_BASIC_AUTH_ACTIVE=true
N8N_BASIC_AUTH_USER=<usuario>
N8N_BASIC_AUTH_PASSWORD=<senha>
N8N_HOST=0.0.0.0
N8N_PORT=5678
WEBHOOK_URL=https://<seu-dominio>/webhook/Frequently asked questions
Short answers for publishing images with less trial and error.
How do I know which port to provide?
Use the port your application listens on inside the container, such as 5678 in the n8n example.