CloudJod documentation
What CloudJod is, the few ideas it is built on, and how to go from nothing to a running app.
CloudJod runs the software your organization builds and uses. You give it your code (a Git repository, a folder from your computer, or a container image) and it builds it, runs it, and gives it its own HTTPS address. It also runs your databases, installs ready-made software in one click, and keeps your team's access, secrets and history in one place. Everything can run on CloudJod's servers, on servers of your own, or on both.
The ideas, in one minute
- Organization
- Your team's account: its people, apps, databases, servers and plan. You can belong to several and switch between them at the top of the dashboard. A large organization can have departments (POS, HR, Sales), each with its own apps and people, on one plan and one bill.
- Project
- One system you run, such as a shop, a point of sale or a CRM, with all of its parts: its website, its API, its background workers and its databases. Apps, one-click installs and databases are created inside a project, and opening one shows the whole system.
- App
-
One program that runs: a website, an API, a worker. Each has its own
address,
https://<app>.<organization>.cloudjod.com, its own logs, settings and history of releases, and can run as several copies. - Database
- A Postgres or Redis database that CloudJod runs for you. Connect it to an app and the app is given its connection string.
- One-click app
- Ready-made software (WordPress, Ghost, Grafana, Uptime Kuma and more) installed in one step. You can also turn your own apps into templates your team installs the same way.
- Develop
- Your organization's workspace for building, testing and looking after every app: chat about your code with the AI provider you choose, one shared memory for coding assistants, and pipelines that build and test every push. Your team opens it as themselves, with no second account.
- Cluster
- A group of your own servers, from any provider or in your own building, joined to CloudJod with one command. Apps can run there instead of on CloudJod's servers.
From nothing to a running app
- Create an account. Your organization is made with it.
- Open Projects and create a project for what you are about to run, or use default.
- Press + New app. Give it a name and the port your program listens on.
- On the app's Deploy tab, connect a Git repository, upload a folder, or name an image.
- When the build has finished and the app shows running, open its address. Its Logs tab shows what it prints.
Getting started goes through each step.
The guides
- Getting started An account, a project, and your first app running at its own HTTPS address.
- Apps Deploying from Git, a folder or an image, and everything an app's page does: builds, releases, settings, scaling, commands, domains and who can open it.
- Databases Postgres and Redis for your apps: creating one, connecting an app, and what happens to the data.
- One-click apps Installing ready-made software in one step, and making templates of your own.
- Develop Your organization's workspace for building, testing and looking after every app, signed in as yourself.
- Your own servers Clusters of your own machines, attached with one command, and choosing where each app runs.
- Teams and access Organizations and departments, roles and areas, approvals, invitations, and the audit log.
- Security How your apps are kept apart from everybody else's, how secrets are kept, and how to protect your account.
- The CLI and the API Everything the dashboard does, from a terminal or a script.
- Plans and limits What each plan includes, what counts against it, and how usage is measured.
Where things are
| The dashboard | https://api.cloudjod.com |
|---|---|
| The API | https://api.cloudjod.com/v1 (see The CLI and the API) |
| Your apps | https://<app>.<organization>.cloudjod.com |
| The command-line tool | curl -fsSL https://api.cloudjod.com/install/cli.sh | sh |
Next: Getting started