Cliodot treats release as a first-class operation. Development and production stay separated; production only receives promoted snapshots.
Two-environment model
- Development: Mutable. Experiment, connect to sandboxes, iterate privately.
- Production: Immutable via direct edit. Stable for live traffic. Only promoted snapshots enter here.
Promotion confirmation
Promoting should be intentional.
- Initiate: Click Promote. The system checks that there are changes to deploy.
- Promotion confirmation:
- Identity verification: Type the workflow name to confirm the correct service.
- Responsibility check: Confirm that the workflow has been tested and that you accept responsibility for the release.
- Human verification (CAPTCHA): Enter a generated code to prevent accidental clicks.
- Deployment: On success, the development snapshot is copied to production atomically.
Hardcoding credentials is a security risk. Cliodot provides environment variables and secrets per project.
- Variables: Non-sensitive configuration (e.g.,
SUPPORT_EMAIL,BASE_URL). Visible to the team. - Secrets: Sensitive credentials (e.g.,
STRIPE_SECRET_KEY,DB_PASSWORD). Encrypted at rest and not readable back in the UI after save. - Context-aware: Define
API_URLonce; set sandbox for development and production for live. The workflow picks the value for the environment where it runs.
Settings and administration#
- General: Application name and branding.
- Team: Invite members and manage permissions (Admin, Editor, Viewer).
- Billing/Subscription: Manage plan and usage quotas (workflow runs, active connectors).