PlanSignal
PlanSignal exposes plan and entitlement facts at read time. It maps billing events and operator-defined plan mappings into JSON your application can query before deciding what to do.
Use it for subscriptions, account tiers and plan-derived feature facts. Your application can include these facts in StateMirror evidence. StateMirror accepts application-defined JSON without any Signal.
Returned facts
- Account status such as active, canceled or past_due
- Plan identifier
- Entitlements derived from stored plan mappings
- Billing state mapped into application-readable JSON
PlanSignal runs in your environment with PostgreSQL. Reads perform a lookup without mutating state or executing side effects.
Application boundary
Plan state is not authorization. Your application owns identity, access control, feature gating and billing collection. PlanSignal does not grant features, revoke access or charge accounts.
Before executing a paid feature, query the current facts and evaluate them with your own rules. Define how the application behaves when plan state cannot be confirmed.
Failure modes
- Delayed billing events or failed webhooks leave stored state stale.
- Incorrect plan mappings produce incorrect entitlement facts.
- Partial writes can leave reads incomplete.
- Network or database failures can prevent reads or cause timeouts.
Technical specification · Application example · Printable datasheet
Formerly SaaS Engine. Existing routes remain available.