The project
Built around an independently useful Core.
Prontera starts with a practical problem: keeping existing Docker applications updated while making changes easier to inspect and recover from.
Where the project stands
Early development, with a defined direction.
Prontera is being built by Ramon Oliveira. The code repository is currently private while release preparation continues. Apache-2.0 is selected for the intended public Core release; that licensed release has not yet been published.
The planned Core release is intended to remain useful on its own. Prontera Cloud adds hosted coordination for people who need a shared workflow across projects, reviewers, and hosts.
- Founder
- Ramon Oliveira
- Core
- Development
- Cloud
- Planned
- Intended license
- Apache-2.0 · public release planned
Product responsibilities
Local operations. Optional hosted coordination.
Prontera Core
Watch container images, apply update policies, check health, and inspect the outcome from a local interface or CLI. The intended open-source release remains useful without a Cloud account.
The current controller manages existing watched containers. The Compose reference deployment installs Prontera and its proxy; it does not provide arbitrary application-stack provisioning.
Read the Core capability inventoryProntera Cloud
The planned service connects existing servers, requests private previews, gives reviewers access, and lets coding agents request permitted operations through the same control plane used by a team.
Applications run on designated customer infrastructure. Cloud coordinates projects and access. An AI agent is optional, and production approval remains a separate decision.
Explore the Cloud roadmapThese capabilities exist in the development code. Production qualification, private-registry pull authentication, and interrupted-update recovery are still being completed.
Restoring a container image does not undo database migrations or application-data changes.
Business model
A useful self-hosted Core. Optional paid Cloud coordination.
The planned public Core release will use Apache-2.0 and operate without a Cloud account. Cloud plans will cover hosted coordination, collaboration, and operational convenience. Customers supply and pay for their own servers, registries, and any external execution services.
We are preparing a small design-partner pilot before an invitation-only beta. The first pilot will focus on a solo SaaS developer, a small SaaS team, and an experienced self-hoster. Prices and usage allowances are still being evaluated.
The product direction is non-destructive billing: a payment problem must not stop customer workloads or remove local recovery, cleanup, revocation, or export paths. Exact Cloud grace policies are still being defined.
Join the preview waitlistContact
Contact the founder.
Share how you run containerized applications, what makes updates difficult, or what you need from a private preview workflow.
prontera@ramonoliveira.xyzFor a security concern, read the security reporting page. For waitlist data requests, read the privacy notice.
FAQ
Practical questions.
Is Prontera ready for production?
Not yet. The Core has working development functionality, but production qualification and important recovery and authentication work remain. Cloud access is not available yet.
Can I use it without Prontera Cloud?
The intended public Core release is independently useful and self-hosted. Cloud is optional hosted coordination, not a required account for local operation.
Will Prontera host my application?
The planned native workflow runs applications on your designated servers. Prontera Cloud coordinates operations and access; it is not a replacement hosting provider.
Do I need an AI agent?
No. Agent access is an additional interface to the planned workflow. Developers and CI can use the same operations without an AI model.
Will agents receive SSH or unrestricted Docker access?
That is not the product model. Planned agent access is limited to named operations and resource scopes, with separate approval where required.
Can anyone’s pull request run on my server?
Not in the initial native-preview model. The plan requires eligible customer-controlled revisions, trusted CI evidence, and approved templates. Untrusted execution needs a later, separately qualified isolation path.
Does rollback restore the database too?
No. Replacing an application image does not undo migrations or data changes. Application-data compatibility and recovery need their own plan.
Is Podman supported?
Not yet as a qualified runtime. Docker is the first target. Rootful Podman, then rootless Podman, are later qualification tracks.
What happens to a preview after review?
The design includes removal when its pull request closes or its lifetime expires. Cleanup must report incomplete work instead of implying that every resource was deleted.
Are you building a sandbox provider?
No. External sandbox or microVM services may be integrated later. Prontera is not building a competing microVM deployment platform.