Features

Project storage

Source files are stored on the Cloudexa NAS and used directly as the deployment source.

Direct file storage: Upload, edit and remove project files from the dashboard.
NAS-backed source: Project files are stored centrally and read during deployment.
Source browser: Browse directories and open files in the web interface.
Browser editing: Edit existing files or create new ones and save changes in place.
Deployment history: Review recent deployments, runtime state and build logs.

Deploy an application from the files stored with your project.

01 Checkout Cloudexa reads the current files from project storage.
02 Sync source Tracked source changes are applied to the project's persistent application directory.
03 Build Dependencies and build output are prepared against the persistent application files.
04 Start container The application starts with the resource limits assigned to the account plan.
05 Route traffic The service is exposed through its Cloudexa hostname or a connected custom domain.

Persistent application storage: Runtime-created files remain available when the container is replaced.
Environment variables: Keep configuration and secrets in environment variables injected at startup.
Build and runtime logs: Inspect deployment output and application logs from the project page.
Custom domains: Use the generated Cloudexa hostname or connect your own domain.
Storage browser: Browse persistent application files and preview supported text files.

Create databases from the same account used for your hosted applications.

PostgreSQL: Create PostgreSQL databases with generated credentials and web access through pgAdmin.
MySQL: Create MySQL databases with generated credentials and web access through phpMyAdmin.
Connection details: Host, port, database name, username, password and DATABASE_URL are listed on the database page.
Password reset: Replace database credentials when an existing password needs to be invalidated.

The rest of the platform stays deliberately straightforward.

Multiple runtimes: Deploy Node.js, Python, PHP, Ruby, Go, Java and static sites.
Project controls: Deploy, redeploy and stop applications without direct access to the Docker worker.
Normal and Premium plans: Hosting limits scale by plan, including running instances, memory and CPU.
API: Use API tokens to read account, hosting, deployment and database information programmatically.