ReelierDocs
GitHub

Cloud

Reelier Cloud (reelier.com) is an optional home for your run receipts — nothing about the CLI or the engine requires it. It exists so a skill’s pass rate, escalation history, and token spend accrue in one dashboard instead of living only in local .reelier/runs/*.jsonl files.

Illustration of the Reelier Cloud dashboard: a sidebar with Overview, Skills, Schedules, Runs, and Settings; five summary cards for runs, passed runs, verified steps, LLM tokens, and skills; and a recent-runs list showing passed receipts with per-step checks and a share action.Reelier CloudOverviewSkillsSchedulesRunsSettingsMHMaxime H.@maximehOverviewRuns128stored recordsPassed runs121of 128 runsSteps verified5123 uncheckedLLM tokens24.6k18.2k + 6.4kSkills9recordedRecent runsview all →✓ passedsf-post-deploy-smoke1.2sShare✓ passedreelier-init-demo210msShared✓ passednightly-backup-check640msShare✓ passedweekly-report-sync890msShare

What you get when you sign in: runs, schedules, and shareable receipts, all in one dashboard.

Sign in

Sign in with GitHub. Reelier Cloud requests only read:user and user:email — the minimum scopes to identify you. It never requests access to your repositories.

Getting your API key

Your first sign-in mints an API key, shown once — save it then, it won’t be shown again (only its hash is stored). Lost it? Regenerate from the dashboard any time.

Pushing receipts

reelier push is fully opt-in — nothing is ever pushed, no network call is ever made, unless both env vars below are set:

export REELIER_CLOUD_URL=https://www.reelier.com
export REELIER_CLOUD_KEY=<your key>
reelier push skills/<your-skill>.skill.md

The skill file itself uploads automatically on its first push from a given working directory; after that, only new run records sync. A local cursor file tracks what’s already been sent, so running push repeatedly is cheap and never re-sends what already made it to the cloud. Full mechanics in the CLI reference.

Schedules

Reelier Cloud can replay a pushed skill on a schedule (hourly, or a fixed daily time) and record the outcome — the same run-record shape as a manual reelier run. Today this is set up on request rather than through a self-serve dashboard control; the dashboard shows schedule status once one exists.

The free tier

Reelier Cloud’s free tier is generous — there’s no hard usage cap enforced today. The dashboard shows your run count for visibility, not as a limit.

Your data

Your skills are plain Markdown files that live in your own repository — portable, readable, never locked to Reelier. Reelier Cloud stores your GitHub identity, the run records you push, and API keys as SHA-256 hashes only (the raw key is never stored after it’s first shown to you). You can request deletion of your account and data any time — see the privacy policy.

The self-host alternative

Reelier Cloud is entirely optional. The CLI engine — record, compile, replay, self-heal — is AGPL-3.0 and runs fully on your own machine with no cloud dependency at all: skip reelier push and nothing ever leaves your machine. Your traces, skills, and run records stay local, plain files, forever readable without Reelier.

Privacy · Terms · HomeReelier · AGPL-3.0