Built to hold your loyalty data cleanly.
Loom Loyalty is an event-driven loyalty platform. Every record belongs to one organization and one environment, every balance is explained by its ledger, and every release keeps working with the one before it.
Events in, one system of record out.
Your systems send events as they happen. Rules turn each one into loyalty outcomes in real time, and the result flows back to the tools that need it.
Your systems
Apps, stores, data pipelines and AI agents
Events
Sent over the REST API or MCP as things happen
Weave and Patterns
Rules run on each event; audiences stay current
System of record
Ledger, balances, tiers, offers and badges
Back to your stack
Signed webhooks, API reads and analytics
Isolation is the default, not a setting.
Every record carries the organization and environment it belongs to, and every request runs inside the organization and environment of the credential that sent it.
Organizations
Each Loom Loyalty customer is an organization. Your records, API keys and roles belong to your organization alone.
Environments
Every organization has separate environments, such as development, staging and production. Each holds its own customers, balances and events, plus its own API keys and rate limits.
Programs
Programs, with their currencies, tiers, offers, targets and rules, are defined once for the organization and switched on in the environments where they should run.
Need more separation?
Custom Fit clients can run on their own database, or on their own dedicated services, depending on tier and requirements. We scope it with your platform and security leads.
Promote a program. Don't rebuild it.
Because programs live at the organization level, the same concept moves from development to production, or through any stage in between, as it is.
Define it once
Build a program, its rules and its offers one time, then switch them on in each environment where they should run.
Move at your pace
Try a concept in development, prove it in a staging or pilot environment, then take it to production without recreating anything.
Schedule and approve
Each promotion can carry a start and end date, and can wait on an approval request before it goes live.
Know who did what, and why a balance moved.
Single sign-on
Connect your identity provider so your team signs in with it.
Scoped roles
People, machine clients and API keys get only the permissions their role grants.
Audit trail
Changes are recorded as audit events you can list and review.
Traceable outcomes
Trace any event to see which rules ran and what they did.
Encryption, data handling and how AI uses member data are on our security page.
Releases that keep your integration working.
Backward compatible by rule
Every release works with the one before it. Fields and endpoints are added first and retired later, never broken in place.
Tested before production
Each release runs in a staging environment and passes smoke tests before it reaches production.
Open status
Uptime and incident history are public on our status page.
Yours to read, export and delete.
Your program data belongs to you. Read any of it through the API, stream changes out through webhooks, and export or delete it whenever you want. We do not sell it, and we do not share it with other customers.
Bring us your hard questions.
Book a call to go through data, access and rollout with the people who built it. Want to see code first? Start on the developer page.