What CloudRaker is
CloudRaker is a platform where you and a built-in AI assistant work together to get repetitive, document-heavy office work done — intake, invoice processing, contract review, vendor onboarding, claims, and the like. Your work lives in a space. An admin defines a reusable process once as a playbook; the AI assistant runs it and drafts the outputs — reading documents, filling forms, drafting records. But you always review and approve before anything becomes real data.
Who it’s for
CloudRaker is built for business and operations teams who run document-heavy, multi-step processes. You do not need to be technical. If your job involves collecting files, pulling data out of them, filling forms, and producing documents — over and over — CloudRaker is for you.
The one rule that defines CloudRaker
The assistant drafts; you decide what to approve. The AI assistant and automated steps never commit data on their own. They produce drafts — proposed records, filled forms, generated documents — and a person reviews, edits, approves, or rejects before anything becomes committed data.
Every extracted value, every filled form, and every record starts as a draft.
How the pieces fit together
Your organization is your whole workspace. Inside it, the work happens in spaces — a space is a workspace that holds files, records, and people for one body of work. Every space is created from a space type, a reusable template that an admin sets up. Admins also define reusable playbooks (an ordered process the agent can run) and install actions (single-purpose capabilities like extract, fill a form, or sign). When you run a playbook inside a space you get a run, made of tasks the agent works through, producing drafts you approve.
A few relationships to keep straight:
- A space is where work happens. A space type is the template a space is created from — admins manage space types; you work in spaces.
- A playbook is a blueprint defined once at the org level. A run is one execution of that playbook inside a space. You can run one playbook many times.
- The agent does the drafting inside a run; a person approves before any AI-produced value is committed.
For a one-line definition of every term — space, space type, playbook, run, record, action, grounding — see Key concepts.
Signing in
You sign in to CloudRaker at app.cloudraker.com with your work account. Sign-in is handled by your organization’s identity provider — there is no local CloudRaker password to set or reset. Visit any page while signed out and you’ll be sent to sign in, then returned to where you were headed.
One organization, one tenant
Everything you see — spaces, files, records, roles — belongs to a single organization. If you’re a member of more than one, switch between them from the switcher at the top of the sidebar. Switching re-scopes the entire app to the other organization and reloads, so nothing carries across.