OpenClix
Open-source, local-first mobile engagement automation that runs on-device with config-driven retention flows, no backend or proprietary SDK required.
At a Glance
Pricing
Fully open-source under MIT license. No cost, no backend required, no proprietary lock-in.
Engagement
Available On
Listed Mar 2026
About OpenClix
OpenClix is an open-source, local-first mobile engagement automation tool that lets builders ship retention flows — onboarding nudges, streak reminders, and re-engagement logic — without backend infrastructure or proprietary SDKs. It uses a config-driven model where engagement rules are defined in a single JSON file and run entirely on-device, giving teams full ownership and auditability. OpenClix is intentionally agent-friendly, with explicit interfaces, clear edit points, and legible folder structures that allow AI agents to safely read, modify, and extend engagement rules.
- Local-first execution: All engagement logic runs on-device — no hosted control plane, no auth/API key required for local-first use.
- Config-driven rules: Wire a JSON config file with app events so rules react dynamically without any backend plumbing.
- Vendored source model: Install via
npx skills add openclix/openclixto bring client code directly into your repo as checked-in source you fully own. - No proprietary lock-in: MIT-licensed, forkable, and auditable — no SDK runtime dependency or vendor control plane.
- AI agent-friendly architecture: Legible folder structure, explicit interfaces, schemas, examples, and fixtures make it safe for AI agents to iterate on engagement logic.
- Local notifications & in-app messaging: Trigger on-device notifications and in-app messages with debuggable reasons and safe edit points.
- Flexible config delivery: Serve
openclix-config.jsonfrom app resources or any HTTPS endpoint for dynamic rule updates. - Broad use cases: Designed for indie builders, product teams running retention experiments, agencies reusing engagement foundations across clients, and agent-first builders.
Community Discussions
Be the first to start a conversation about OpenClix
Share your experience with OpenClix, ask questions, or help others learn from your insights.
Pricing
Open Source
Fully open-source under MIT license. No cost, no backend required, no proprietary lock-in.
- Local-first on-device engagement logic
- Config-driven retention flows via JSON
- Vendored source model
- Local notifications and in-app messaging
- No backend or hosted control plane required
Capabilities
Key Features
- Local-first on-device engagement logic
- Config-driven retention flows via JSON
- Vendored source model (no package runtime dependency)
- Local notifications and in-app messaging
- No backend or hosted control plane required
- MIT open-source license
- AI agent-friendly architecture
- Debuggable rule reasons and safe edit points
- HTTPS or app-resource JSON config delivery
- No proprietary SDK lock-in
