Managed App includes service wiring
Moltaro provisions the app with a cloud provider and keeps Google Maps key, SMTP sender, protected secrets, URLs, versions, backup/update flow, and capacity changes under Portal-managed operations.
Deployment & Pricing
Deployment & Pricing
Choose the operating model by deciding who owns service wiring: Google Maps key, SMTP sender, protected secrets, database backups, capacity growth, and updates.
Service ownership
Google Maps, SMTP, database backups, capacity, and secrets are part of the deployment decision.
The application is not really installed just because containers started. It also needs external keys, mail delivery, protected config, database backup responsibility, and a repeatable restore/update path.
Managed App
Self-hosted
Google Maps API key
Moltaro uses the configured managed key policy and keeps the key attached to the installation.
You bring the key, billing project, restrictions, rotation process, and incident response.
SMTP sender
Moltaro configures sender credentials for the managed installation and includes them in the operational workflow.
You configure SMTP credentials plus SPF, DKIM, DMARC, bounce handling, and deliverability checks.
Secrets and runtime settings
Portal stores protected install metadata and exposes URLs, versions, status, and update progress.
You keep appsettings, DataProtection keys, license files, Docker volumes, and restore notes consistent across environments.
Database backups
For the planned DigitalOcean path, the managed database baseline includes daily backups with point-in-time recovery; Moltaro owns upgrade safety flow and customer-facing restore policy.
You schedule PostgreSQL backups, choose storage and retention, protect dumps, and test restore before you need it.
Capacity scaling
Cloud resources can usually be resized through provider tooling; DigitalOcean managed databases support cluster resize and storage autoscaling.
You plan hardware, move containers, database volumes, files, full-text data, paths, and downtime when the local server no longer fits.
Self-hosted means you own service setup
Your team supplies and maintains the Google Maps API key, SMTP credentials, DNS/mail authentication, DataProtection keys, database/files/full-text volumes, backups, restores, hardware moves, and updates.
01
What to choose
The same product, different service ownership.
Runtime model, governed records, modules, and package path stay aligned. What changes is who maintains credentials, volumes, backups, and update flow after installation.
Managed App
Use Managed App when the team wants Moltaro to operate the installation, configure service dependencies, and expose Portal progress, URLs, version metadata, and support flow.
- Fastest path to a hosted production pilot.
- Moltaro owns install orchestration, protected configuration, external service setup, provider database backup baseline, updates, and capacity-change workflow.
- Less direct infrastructure control; long retention, downloadable backups, and custom service policies are commercial options.
Self-hosted
Use self-hosted when policy, customer contracts, local debugging, or data-residency rules require your team to operate the stack and its service dependencies.
- Maximum runtime, database, network, key, SMTP, backup, and hardware-capacity control.
- Works for local Docker, customer servers, and production environments you manage.
- Your team owns upgrades, service credentials, storage, restores, monitoring, server moves, and incident response.
02
Comparison
Compare the operating model before the invoice.
Responsibility
Managed App puts install, service wiring, and runtime operations under Moltaro orchestration. Self-hosted keeps those duties with the customer or implementation team.
Control
Self-hosted gives direct control over containers, database access, volumes, secrets, DNS, SMTP, Google Maps key, and local debugging. Managed App trades some control for speed.
Backups
Managed App uses provider database backup mechanics plus Moltaro upgrade safety flow. Manual downloads, long retention, and storage quotas are separate commercial choices.
Updates
Managed App updates are orchestrated through the Portal. Self-hosted updates are run by your operators with the package and moltaroctl runbooks.
Debugging
Self-hosted makes it easiest to attach Visual Studio, reuse local settings, mount files and full-text data, and reproduce production issues with local containers.
Capacity scaling
Managed App can usually grow through provider resizing and storage autoscaling. Self-hosted growth means planning hardware, moving volumes, validating config, and accepting migration risk.
Cost model
Self-hosted starts free and can move to perpetual licensing. Managed App is monthly and includes hosted operations, with add-ons for storage, backups, and support depth.
03
Packages
Temporary package prices for discussion.
These prices are placeholders while the packaging model is refined. They make the deployment tradeoffs visible enough to evaluate.
Self-hosted Free
$0 forever
- Perpetual local runtime license.
- Limited storage and active-record volume.
- Customer operates infrastructure and backups.
Self-hosted Unlimited
$1,499 one-time
- Perpetual on-premise license.
- No runtime storage or active-record limits from the license.
- Best when updates are handled separately.
Self-hosted Updates
$499/year maintenance
- Access to package downloads published during maintenance.
- Release support for customer-managed upgrades.
- Runtime keeps running when maintenance ends.
Managed App Starter
$99/month
- Hosted Moltaro runtime for a small production pilot.
- Portal-managed install and update progress.
- Standard provider backup baseline.
Managed App Team
$249/month
- More operational volume and support attention.
- Suitable for a team-wide governed workflow.
- Optional backup retention and download add-ons.
Managed App Operations
$499/month
- Production operating package for heavier workflows.
- Stronger update planning and operational support.
- Backup/storage policy sized during rollout.
Enterprise and regulated
Custom
- Security review, procurement, and deployment constraints mapped together.
- Can include customer-managed hosting, managed cloud, or hybrid support.
- Commercial terms depend on scope, storage, support, and retention needs.
04
01
02
03
04
Backups and updates
Backup policy follows who operates the environment.
Provider baseline
For Managed App, the cloud provider handles base managed database backup mechanics while Moltaro owns the customer-facing orchestration and restore policy.
Upgrade safety
Before managed updates, Moltaro should create short-retention safety backups as an operational protection, not as a separate paid product line.
Manual and long retention
Downloadable backups, long retention, compliance retention, and storage-heavy restore points are paid or quota-based because they create storage, egress, and support cost.
Self-hosted responsibility
For self-hosted deployments, the customer or operator owns PostgreSQL dumps, file storage, full-text data, Google Maps key, SMTP sender, DataProtection keys, license files, hardware capacity, and restore testing.
Next step
Need help choosing the operating model?
Tell us whether you need a managed cloud path, a self-hosted pilot, or a production rollout with strict service, backup, and update requirements.