Rykloud runs your projects in environments on the cloud you choose: databases, Redis, buckets, services built from Git or an image, secrets and custom domains, each change previewed with its price before it is made. This is how to automate all of it. The API has 175 operations in 16 areas at https://api.rykloud.com, version 2026-11-05; the CLI is release 0.1.0.
Start in five commands
Install the CLI, sign in with your Rykon account, see your organisations, then ask for an environment. Nothing starts or is charged until an owner approves the price Rykloud states. The quickstart goes on to deploy a service from Git and read its logs.
curl -fsSL https://get.rykloud.com/install.sh | sh
rykloud auth login
rykloud orgs list
rykloud envs create staging --cloud any --area eu --size general-s
rykloud envs watch stagingWhat you can automate
- EnvironmentsAsk for one at a size and place, approve its price, stop it to zero, wake it, update it, destroy it.
- Resources and changesPostgres, Redis, buckets, services, secret groups and domains, each change previewed, priced and applied.
- Builds and deploysBuild a branch head or a commit, follow the log, roll back to a kept deploy, restart.
- Networking, backups, schedulesFixed outgoing addresses, VPN keys, private links, backups and restores, stop and start on a schedule.
- Organisations and peopleInvite people, change roles, hand over ownership, move a product to another organisation, export the audit record.
- Activity, billing and statusWho did what and what it cost, usage and spending limits, notifications, Rykloud's own status.
Two ways in
- The rykloud CLI for people and scripts: every command is an operation of the API, with stable
-o jsonand-o yamloutput and documented exit codes. CLI reference. - The REST API for your own code: JSON over HTTPS with a bearer token from a CLI session. Authentication says how to get one, and what programs can use today.
Learn how it works
- ConceptsOrganisations, projects, environments, resources, previewed changes, approvals, backups and the record.
- Errors and referencesOne error shape, stable codes, which to retry, and the req_ reference support asks for.
- Retries and idempotencyWhat is safe to send again, and why an approved change cannot happen twice.
- Rykon Mail and Rykon AIThe products inside Rykloud have their own APIs and docs, with the same Rykon account.