Running your code should not take five other services
REM CloudHub is one place to build, run and look after the software a team writes: from a git branch to a running address, with everything it needs beside it.
What REM CloudHub is
You connect a repository from GitHub, GitLab or Bitbucket and pick a branch. REM CloudHub builds it, runs it at a real address, and keeps its databases, files, secrets, scheduled jobs and AI keys in the same project. One console, one sign-in, and a record of every change.
It is built for teams that ship small internal tools, data apps and services often, and would rather spend their time on the code than on the plumbing around it.
Why we built it
Getting one app online usually means a build service, a host, a database provider, a secrets store, a scheduler and an AI provider account, each with its own login, bill and audit trail. When something breaks, the answer is spread across all of them.
We wanted one place where a person can see what is running, who changed it and why, and go back to the version that worked, without asking the one colleague who set it all up.
What it does differently
- Deployments are records. Each one keeps its commit, its build log and how it ended. Rolling back is choosing an earlier row.
- Resources belong to a project. Postgres databases, caches, file storage and jobs sit with the project that uses them, each with its own login.
- Secrets stay out of images. RCH Vault keeps them encrypted and hands them to a container when it starts.
- One model name for AI. Apps call a name such as rch-advanced; the RCH AI Gateway tries the provider keys behind it in order.
- Agents with a preview. The built-in MCP server lets AI agents work with the permissions of the person who connected them; anything that changes something is previewed and confirmed first.
- Failures in plain words. The error map turns an error code into a sentence and a reference you can search for in Activity.
Part of REM Platforms
REM CloudHub is one of the REM Platforms products. You sign in to all of them with one account (REM Auth), AI usage is paid from one balance of REM credits, and the documentation, user guides and blog live in one place.
What we hold ourselves to
- Show the reason. Every refusal, limit and failure says why, in words a person can act on.
- Nothing hidden in the bill. A plan lists its limits; AI usage is metered per call and shown per key, model and day.
- People decide. AI suggests and helps; changes wait for a person's confirmation.
- Your data is yours. Your code, databases, files and logs are used only to run your projects.
Who is behind it
REM CloudHub is built and run by REM Workers Private Limited, India. Questions, partnerships or feedback: support@remplatforms.com or the contact page.
Bring a repository
Create your account, connect your git host and watch the first build log.