Step 5: Deploy

After completing Steps 1–4, your application is defined and your users are onboarded. Step 5 is choosing how the platform runs. There are two options: hosted by DuploCloud or self-hosted in your own infrastructure. The application and its capabilities are identical in both cases — the difference is where it runs and who operates it.

Hosted by DuploCloud

DuploCloud handles deployment, scaling, operations, uptime, and security. Your application runs in DuploCloud's cloud. You define resources, write skills, and serve your users — DuploCloud manages everything underneath.

This is the default path and the one that enables a true product-led growth motion: sign up, define your domain, and ship a working application without touching infrastructure. It is well-suited for getting started quickly, for non-sensitive domains, and for scenarios where you want to demonstrate value to stakeholders before a formal procurement conversation.

Self-Hosted

Download a Kubernetes manifest with Docker images and run the entire platform in your own infrastructure. Same application, same capabilities, full control over the environment. You are responsible for deployment, scaling, and operations.

Self-hosted is the right choice when your application operates on production infrastructure with privileged credentials — DevOps and SecOps platforms in particular. It is also the right choice for regulated industries with data residency requirements and for organizations whose security policies prohibit sending operational context outside their network boundary.

Choosing Between Options

Start with hosted to validate your application. Define your policy model, write your skills, onboard a pilot team, and confirm that the application delivers value in your domain. If your security requirements ultimately demand that the platform run within your own boundary, migrating to self-hosted is a configuration change — the application definition, skills, and resource data move with you.