Public and private repositories
Create open repositories or keep project source private to your Cloudexa account.
Cloudexa brings repositories, deployments, persistent application storage and custom domains into one workflow.
Keep source code, history and browser-based repository tools beside the services that run from them.
Create open repositories or keep project source private to your Cloudexa account.
Clone, pull and push with familiar Git commands instead of a platform-specific workflow.
Browse directories and files directly from the repository interface.
Follow commit messages, authors and repository history from the web.
Change existing files and commit those updates without opening a local editor.
Create and delete repository files directly through Cloudexa when making smaller changes.
Cloudexa detects the runtime, applies source changes to persistent project storage, builds the application and starts it in an isolated container.
Applications run separately with plan-based CPU, memory and process limits.
Runtime-created files survive container restarts and redeployments instead of disappearing with the container.
Keep application settings and secrets outside the repository and inject them at runtime.
Inspect deployment output and application logs from the project dashboard when needed.
Connect your own hostname and manage DNS and certificate setup from the hosting project.
Browse the actual persistent application files, directories, sizes and text-file previews from the dashboard.
Repositories and hosted applications remain connected instead of becoming separate pieces of infrastructure to manage.
See repository-linked applications, their state and deployment information from one place.
Deploy, redeploy and stop applications without direct access to the Docker worker.
Use standard hosting limits or Premium resources for projects that need more instances, memory and CPU.
Manage repositories, hosting projects and account settings from the same user profile.
Give deployed services a public Cloudexa address without manually exposing container ports.
Keep build commands, start commands, ports and runtime configuration explicit when a project needs customization.
Start with a repository and turn it into a running project when you're ready.