Design Tier 2 — ComposedIn the lab
Creytix Routines
A marketplace for recurring operational work.
A routines catalog, marketplace, and dispatch system for recurring operational tasks.
Recurring work shouldn't need to be re-invented each time.
What it does for you
Cataloged, not re-invented
Recurring operational tasks live in a shared catalog instead of being rebuilt by whoever picks them up next.
Dispatch-driven
Routines dispatch on a schedule instead of relying on someone remembering to kick them off.
Report-only where it matters
Fleet-health routines write reports and never push, delete, or auto-fix on their own — findings go to a human before anything changes.
Capabilities
- Routines catalog
- Marketplace listing
- Dispatch scheduling
- Creytix Go companion app
- Report-only fleet-health scripts
Proof, not adjectives
- 4 of 8 planned scripts shipped
- Dependency audit, uptime sweep, broken-link check, and stale-branch report are built and running; 4 more are deferred pending unverified dependencies (Time Machine access, Cloudflare API auth, a Lighthouse/Chrome install, and an analytics data source).
- Non-destructive by design
- Shipped routine scripts only ever write to a reports directory — they never push, queue jobs, or delete anything.
Related tools
Built with Creytix, on Creytix
This page itself was produced by the platform it describes — the same design tokens, module pipeline, and review gates used for every Creytix client site. Nothing here is a mockup of the product; it is the product.