PlanSignal [ID: PLN-01]
Note: PlanSignal replaces the former “SaaS Engine” name. Route compatibility is retained.
PlanSignal is a self-hosted plan and account state engine.
It pulls billing truth from your payment provider and exposes deterministic internal state your application can consult at runtime.
PlanSignal does not authenticate users, authorize actions, or enforce access control.
It emits plan and account state only. Your code must decide what to do.
What it emits
- Account status (active, canceled, past_due, etc.)
- Plan and entitlement state
- Billing truth mapped into internal application state
What it does NOT do
- Does not block requests
- Does not revoke access
- Does not enforce billing or permissions
- Does not act as a security system
Typical use
Before executing a paid feature, your application queries PlanSignal for current plan state and explicitly decides and executes behavior in your own code.
Important
Absence of a restriction is not permission.
SimpleStates emits state. Your system implements outcomes.
If state cannot be confirmed, your application must handle the outcome explicitly.
Self-hosted. Signal-only. No SLAs. No emergency support.
Failure modes
- Billing event sync is delayed or missing → state can be stale
- Plan mapping is misconfigured → emitted plan state can be incorrect
- Partial writes / database inconsistency → reads can be stale, incomplete, or incorrect
- Network/database failure → reads can fail, time out, or return unexpected data
- Interpreting emitted state as enforcement → your application can allow behavior when it should not