DeployOn Open console

FROM CODE TO CLOUD

Your app.
Your database.
Online.

Bring your code, connect your data, and give your project a live HTTPS address. DeployOn brings the work of launching and running an application into one place.

Apps · Self-hosted tools · Databases

DeployOn cyan Saturn emblem with its original white ring
CODE → CLOUD

ONE PLATFORM. YOUR NEXT STEP.

What are you building?

Start with the task, not the infrastructure.

01 / DEPLOY CODE

A repository becomes
a running application.

Choose your source, branch, and service port. Configure the build and start commands your application needs, then deploy. Use the framework guides to check the setup before your first release.

Working with an existing Dockerfile? Keep control of your container build. Prefer a supported framework workflow? Follow the relevant guide rather than starting from an empty infrastructure configuration.

Read the quick start

Your deployment checklist

  1. Connect the sourceChoose the repository and branch you want to ship.
  2. Set the essentialsAdd environment variables and confirm the listening port.
  3. Check the releaseRead the build output, inspect logs, and open your application.

02 / LAUNCH TOOLS

Give useful software
a place to run.

Start from a preconfigured template when your project needs an established tool. Explore WordPress for a website, n8n for workflows, or Ghost for publishing. Grafana, Uptime Kuma, and MinIO cover other practical needs.

A template is a starting point, not a substitute for ownership. Review the application's configuration, access settings, storage requirements, and update process before inviting people to use it.

Explore templates in the console

Choose around your task

  1. PublishBuild your site or editorial home with WordPress or Ghost.
  2. AutomateConnect the steps in your workflow with n8n.
  3. ObserveExplore Grafana dashboards or Uptime Kuma checks.

03 / ADD A DATABASE

Your application
needs a memory.

Choose PostgreSQL, MySQL, Redis, or MongoDB to match your application's data model. Managed databases give you a dedicated service with persistent storage and connection details to use in your app.

Database services are billed separately from application plans. Review the database size and price before provisioning. Keep credentials out of source code, and check the backup guidance before trusting a service with important data.

Explore database options

Connect deliberately

  1. Pick your engineUse the database your application actually supports.
  2. Configure accessUse connection details through environment variables.
  3. Plan for recoveryUnderstand backup coverage and test your restore process.

04 / OPERATE

Ship it. Then
keep it understood.

Use logs and metrics to understand your running services. Check deployment history when a release changes behavior, and follow the troubleshooting guides before making another change.

Prefer the terminal or a coding agent? DeployOn documents CLI setup, authentication, deployments, logs, and infrastructure workflows. Start with the agent guide, choose the intended project, and review the action before it runs.

Connect your coding agent

Keep the next step clear

  1. InspectRead logs and resource metrics before guessing.
  2. UnderstandCompare the service configuration with your application's needs.
  3. ActUse the console or documented CLI workflow for changes.

PLAN YOUR START

A clear monthly starting point.

Compare plan details

Free

$0 / month

Try the platform.

Starter

$8 / month

Take the next step.

Pro

$18 / month

Choose more capacity.

Enterprise

Custom

Discuss your requirements.

Prices in USD. Database services are billed separately. Check current limits and billing details before choosing a plan.

BEFORE YOU DEPLOY

A few useful answers.

Browse documentation
Do I need to buy a domain?

No. A platform app subdomain lets you start without registering a domain. This is not registration of your own domain. Connect a domain you already own; registration and renewal remain separate. Follow the custom domain guide to configure the required DNS records, verify ownership, and check the certificate status. DNS changes may take time to propagate.

Is my database included in the app price?

No. Budget for your application and database separately. Review both services before provisioning so the total reflects the setup you intend to run.

Can I deploy with a coding agent?

Yes. The agent documentation explains the supported CLI workflow. Authenticate, select the correct project and application, then use the documented deployment command. Keep account tokens private and check the target before making changes.

How should I choose a plan?

Start with the resources your application needs, then compare the documented limits. Plan resources are shared across the Team workspace, so consider the services you will run together rather than assuming every app receives the full allowance. Review storage needs, memory use, and your separate database package before committing. If you are unsure, use the documentation to understand each limit and choose a setup you can inspect and manage comfortably.