From a git branch to a running address
Create an account, connect your git host, deploy a branch and add what the app needs. Every step is recorded, so you always know what runs and why.
Six steps to your first project
About fifteen minutes with a repository that already has a Dockerfile.
Create your account
Sign up with REM Auth, the one account for every REM Platforms product. You get your own organisation on the Free plan straight away, with yourself as its Owner. Invite colleagues later, when your plan includes seats.
Connect your git host
Under Connectors, open Git and sign in with GitHub, GitLab or Bitbucket, or paste a personal token; the first step of New project offers the same. RCH clones with your own connection first, so it sees exactly the repositories you can.
Create a project
Open Projects and choose New project. Pick the repository and the branch. With a Dockerfile, RCH builds the image from it as it is; the console lists the other project types it offers.
Deploy and watch the build
Press Deploy. The build log streams line by line. When the container starts, the router gives it an address and the project page shows it running. A failed build names the step that failed.
Add what the app needs
From Resources, add a Postgres database, a cache, file storage or a scheduled job. Their connection details reach the container as secrets from RCH Vault, never baked into the image.
Call AI through one name
Create a key under AI and call a model name such as rch-fast. Usage is paid from your organisation's REM credits; calls on your own provider keys are not metered.
Day to day
- See what changed. Activity lists who changed what, the reason and the result, for people and for agents.
- Get told first. Alert rules watch your projects and notify you in the console or by e-mail.
- Go back. Every deployment keeps its commit and log. Pick an earlier one and RCH runs it again at the same address.
- Run jobs. Scripts on a schedule or on demand, with the output, duration and exit code of every run.
- Share safely. Share secrets with a team, rotate them, and see who read what.
For teams
An organisation's Owner invites people and gives them roles; teams group people and the projects they work on. Each person signs in with their own REM Auth account, and what they can see follows their role. The organisation picked in the switcher scopes everything you see.
For AI agents
Connect an agent to the built-in MCP server with a token tied to a person. It can list, deploy and inspect projects with that person's permissions. Reading is immediate; anything that changes state returns a preview and a confirmation code first. See Developers.
Questions
Do I need a Dockerfile?
It is the direct route: RCH builds your image from it as it is. The console lists the other project types it offers when you create a project.
What does the Free plan include?
Your own organisation with one seat, deploys from git and the AI gateway with a monthly allowance of REM credits. Plans with more seats, teams and limits are on the pricing page.
What happens when the credits run out?
Paid model names pause for your organisation and its admins see why. Projects, jobs, databases and calls on your own provider keys keep working; a top-up or the next cycle lifts the pause.
Where can I read more?
The help centre links to the user guide for every screen, and Getting started walks through the first project click by click.
Start with one repository
Free to start. No card needed for the Free plan.