Choose Moltern when
You want apps, databases, catalog software and private coding agents in one workspace, with scoped access and organization governance.
Discuss your stack ↗MolternMoltern vs Hetzner Cloud
Compare
Moltern vs Hetzner Cloud
Hetzner Cloud provides servers, volumes, networks and infrastructure APIs; your team builds and operates the application platform above them.
Flight paths artwork / 63
A working app rarely runs alone. It has data, background work, secrets and people who need access. Hetzner Cloud provides servers, volumes, networks and infrastructure APIs; your team builds and operates the application platform above them. Compare that starting point with Moltern’s shared workspace before deciding what your team should operate.
Start with the right job.
What Hetzner Cloud is built around
Hetzner Cloud provides servers, volumes, networks and infrastructure APIs; your team builds and operates the application platform above them.
Review notes & documentation ↓42 · feature dimensions
Look beyond the first deployment.
What is included, what depends on a plan, and what your team must assemble or operate.
42 / 42 · rows shown
| Capability | Moltern | Hetzner Cloud |
|---|---|---|
| Build & deploy | ||
| Git deployments | MolternDocumented Repository, branch and build settings | Hetzner CloudYour team operates it You operate the software above the VM |
| Static sites | MolternDocumented Static and server applications | Hetzner CloudYour team operates it |
| Container workloads | MolternDocumented Application builds and packaged services | Hetzner CloudYour team operates it You operate the software above the VM |
| Background workloads | MolternDocumented Run supported app and service processes | Hetzner CloudYour team operates it You operate the software above the VM |
| Environment separation | MolternDocumented Production, staging, development and preview environments | Hetzner CloudYour team operates it |
| Deployment history & rollback | MolternDocumented Release history and application rollbacks | Hetzner CloudYour team operates it |
| Services & data | ||
| Packaged service catalog | MolternDocumented Databases, CMS, analytics, automation and more | Hetzner CloudYour team operates it You operate the software above the VM |
| SQL databases | MolternDocumented Database services with service-specific setup | Hetzner CloudYour team operates it Install, patch and back up the database yourself |
| Caches & queues | MolternDocumented Deploy supported catalog services | Hetzner CloudYour team operates it Install, patch and back up the database yourself |
| Persistent storage | MolternDocumented Workload storage with workspace allowances | Hetzner CloudPlan / configuration Attach durable storage with its own lifecycle Volumes |
| Private service connections | MolternDocumented Select targets and runtime connection variables | Hetzner CloudPlan / configuration Private connectivity requires workload configuration |
| AI service stacks | MolternDocumented Catalog AI services, with workload-specific resources | Hetzner CloudYour team operates it |
| Agent workspaces | ||
| Coding-agent workspace | MolternDocumented Private Codex, Claude Code, Gemini CLI and OpenCode workspaces | Hetzner CloudYour team operates it You operate the software above the VM |
| Agent provider sign-in | MolternDocumented Save supported provider sessions or API keys | Hetzner CloudYour team operates it |
| Per-target agent permissions | MolternDocumented Read context or connect to explicitly selected workloads | Hetzner CloudYour team operates it |
| Browser terminal | MolternDocumented Multiple terminal tabs in private workspaces | Hetzner CloudYour team operates it |
| Persistent agent files | MolternDocumented Optional persistent workspace, within storage quota | Hetzner CloudYour team operates it |
| Remote desktop | MolternPlan / configuration Omarchy desktop profile; availability and host capacity apply | Hetzner CloudYour team operates it You operate the software above the VM |
| Run & observe | ||
| Application & service logs | MolternDocumented Deployment and runtime visibility | Hetzner CloudYour team operates it |
| Resource monitoring | MolternDocumented Workload CPU, memory and status views | Hetzner CloudYour team operates it |
| Automatic instance scaling | MolternPlan / configuration Eligible workloads; min/max instances and CPU target | Hetzner CloudYour team operates it |
| Domains & TLS routes | MolternDocumented Application domains and route configuration | Hetzner CloudYour team operates it |
| Secret handling | MolternDocumented Build/runtime variables; separate use and reveal permissions | Hetzner CloudYour team operates it |
| Event webhooks | MolternDocumented Workspace event delivery and webhook management | Hetzner CloudYour team operates it |
| Identity & governance | ||
| Organizations & workspaces | MolternDocumented Shared organization with distinct workspace ownership | Hetzner CloudPlan / configuration |
| Scoped roles & groups | MolternDocumented Environment and resource scopes, groups and expiry | Hetzner CloudPlan / configuration Project or team-level roles; inspect resource scope |
| SAML / OIDC SSO | MolternDocumented Verified domains, provider checks and SSO enforcement | Hetzner CloudConfirm requirements |
| SCIM provisioning | MolternDocumented Synchronize users and groups; grant workload access separately | Hetzner CloudConfirm requirements |
| Audit history | MolternDocumented Organization security history and audit exports | Hetzner CloudConfirm requirements |
| Access reviews & approvals | MolternDocumented Review access and protected-action requests | Hetzner CloudConfirm requirements |
| Runtime primitives | ||
| Public sandbox execution SDK | MolternDifferent product scope Public discovery endpoints; no supported sandbox execution SDK | Hetzner CloudDifferent product scope Platform management API differs from a sandbox execution SDK Cloud API |
| Platform CLI | MolternDifferent product scope Provider CLIs in agents; standalone Moltern CLI coming later | Hetzner CloudDocumentedhcloud |
| Unrestricted root VM access | MolternDifferent product scope Workload terminals; unrestricted root VMs are not promised | Hetzner CloudDocumentedCloud Servers |
| Environment snapshots & restore | MolternConfirm requirements Persistent files; VM memory snapshots are not documented | Hetzner CloudPlan / configuration Verify disk, memory and resume coverage separately Snapshots · Backups |
| GPU compute | MolternConfirm requirements AI catalog services; confirm GPU capacity for your deployment | Hetzner CloudConfirm requirements |
| Hostile-code isolation | MolternConfirm requirements Private workloads; review hostile-code isolation requirements | Hetzner CloudConfirm requirements |
| Costs & limits | ||
| Budgets & spend guardrails | MolternPlan / configuration Cost centers, budgets and eligible capped PAYG overages | Hetzner CloudYour team operates it |
| Capacity admission & quotas | MolternDocumented Workload slots, CPU/RAM and storage allowances | Hetzner CloudDocumented Configure resource size, quota and lifecycle rules |
| Idle lifecycle | MolternPlan / configuration Hobby may sleep; Pro production has no Hobby sleep behavior | Hetzner CloudYour team operates it |
| On-premises deployment | MolternPlan / configuration Available by arrangement for larger organizations | Hetzner CloudDifferent product scope |
| Billing granularity | MolternDocumented Plan allowances, measured usage and storage views | Hetzner CloudDocumented |
| Backup & recovery responsibility | MolternYour team operates it Service-specific; assign owners and test restoration | Hetzner CloudYour team operates it |
How to read this table
“Confirm requirements” means the reviewed documentation does not establish an equivalent workflow. It does not mean the feature is impossible. Plan and configuration requirements still apply to documented features.
Documented Plan / configuration Your team operates it Separate service / integration Confirm requirements Different product scope
The limits that change the decision.
Check the exact plan and region before committing. Resource limits, lifecycle rules and billing units are different questions.
Capacity & concurrency
Moltern
Apps, top-level services and coding agents count toward workload quota. Agent CPU and RAM are reserved while running; persistent storage uses the workspace pool. Maximum autoscaling capacity must fit available quota.
Hetzner Cloud
Check VM quotas, size availability, regional capacity, volume limits and network throughput. Application scheduling and service-level admission remain part of your platform design.
Runtime & persistence
Moltern
Hobby services may sleep after inactivity. Pro is intended for production without that sleeping behavior. Persistent agent files survive restarts; running processes and in-memory state are not automatically resumed.
Hetzner Cloud
VM and disk lifecycles are separate. Stopping a server is not the same as deleting its disks or backups. Test restart, restore and application failover explicitly.
What goes on the bill
Moltern
Check current in-product plan allowances, measured usage, storage and eligible overages. PAYG has an explicit monthly cap; a budget alert and a hard spending guardrail are different controls.
Hetzner Cloud
Include the instance or bundle, disks, snapshots, public IPs and outbound traffic. Add the application platform, monitoring and operational work your team provides.
- 01
Map the app and its dependencies.
List repositories, workers, data stores, secrets, domains and who owns each one. Keep an export and a rollback route before moving data.
- 02
Build a staging environment.
Deploy the app, attach only the services it needs, and test routes, persistence, logs and access rules with representative traffic.
- 03
Compare the whole operating cost.
Include build time, runtime, storage, network traffic, AI-provider charges and your team’s operating time. Move production only after recovery and ownership are clear.
Review notes & documentation
Reviewed 26 October 2026 against public product documentation. This is a workflow comparison, not a benchmark, certification assessment or guarantee of feature parity. Linked products, enterprise agreements and self-managed installations have their own terms.
Put it into practice
Deploy the code you own
Connect a repository and branch, review the build and start commands, then set the runtime port and health check. Static sites and web services have different operating needs.
Choose the supporting software
The catalog includes data, automation, AI, monitoring and other packaged software. Read each service guide before deployment and review its configuration and dependencies.
Keep agent access scoped
A coding agent is a private terminal workspace. Choose the provider and grant only the app or service context required. No grant means no private resource context.
Detailed instructions are maintained in the product documentation.
Questions before you start
Can I keep my existing framework?
Use a supported runtime or a Dockerfile. Review the application guide for your build output and server requirements.
Does every service have the same setup?
No. Required variables, dependencies, storage and access differ. The individual service guide explains the setup.
Do I need to change coding agents?
Moltern documents several provider CLIs and a generic terminal workflow. Provider sign-in and usage terms still apply.
Keep exploring
All pages ↗
Start with one useful workload.
Bring your code or choose a service, then give the result a clear operating home.
Start building ↗