Memberium · Powered by the Torii engine
One membership platform
Any CRM, or none
The Torii engine flips the relationship between your membership site and your CRM. Your WordPress site becomes the home of your tags, fields, membership levels, and access rules. The CRM becomes a connection you can swap or drop. Membership access, features, and automations keep working no matter which CRM you connect.
- CRMs required to run
- 0
- Standard every CRM uses
- 1
- CRM, swappable in an afternoon
- Any
- Stands on its own
- Full
“No CRM” mode runs a complete membership business.
The tension
“Integrated” turns out to have meant “married”
For a decade, the rule for CRM-connected membership plugins has been the same: pick a CRM, and build your entire business around it. The CRM becomes the brain; the plugin becomes a remote control. That feels powerful right up until the day the business outgrows the arrangement.
The CRM raises its prices
You pay, because leaving costs more than staying, and the tool chosen for leverage becomes a lock-in you never negotiated.
The CRM changes its API
When they change their API, your site goes down through no fault of your own.
The CRM is acquired or stagnates
An acquisition, a shutdown, or a stalled roadmap can take the whole plugin down with it.
A better CRM appears
You can’t move, because moving means rebuilding the membership site: every tag, field, and access rule re-mapped against the new CRM.
The CRM has an outage
Your paywalls and logins go down with it. The CRM is a single point of failure for your revenue.
The shift
Your CRM answers to your site
Your WordPress site holds your tags, fields, membership levels, and access rules itself. The CRM becomes just another connection. Switch it, or run without one.
Membership access, login, and automations are driven by your tags and fields, so they keep working regardless of which CRM is connected.
Your site is in charge
The CRM becomes an optional connection
Your WordPress site holds the tags, fields, membership levels, and access rules itself. The engine talks to the CRM through one standard connection, so it never depends on any one CRM’s quirks.
- Everything works with no CRM connected at all
- “No CRM” is a real mode, a complete membership business without one
- Add a new CRM and your features come along for free
- Your features work the same across every CRM
What this means
Switch your CRM in an afternoon
The Torii admin ships a connector chooser, a single screen where the active CRM is selected from a card grid, including the “No CRM” option. Switching is a deliberate, confirmed action that spells out exactly what happens, and your old CRM’s settings stay intact.
- Tag and field mappings are saved per-CRM; switch away and back, they take effect again
- Logins and connection settings are kept per-CRM, so a switch is reversible by design
- Membership access keeps running throughout, because the rules live on your site
What this means for you
Concrete things you simply could not do before
Freedom to leave
Your settings are saved per-CRM. Switch away and come back without starting over.
Negotiation leverage
When the vendor knows you can leave, you stop paying the locked-in rate, and the renewal conversation changes.
Resilience you don’t have to manage
CRM outage? The site stays up. CRM acquired or deprecated? Pick another connector and carry on.
One system to learn
One admin, one tagging model, one field system, with identical behavior regardless of which CRM is connected.
Start simple, grow on your terms
Launch on standalone “No CRM” mode, prove the model, connect a CRM when the volume justifies one.
The breadth
A complete platform, CRM or not
Pulling away from the CRM lets features ship faster and work everywhere, because they’re all built against one stable layer. And all of it runs in standalone mode.
Access & Membership
- Memberships & Access Control: the paywall and content-gating engine
- Onboarding: guided setup funnel for new members
- Profile Builder: front-end profile editing
Identity & Login
- Passkeys (WebAuthn): passwordless, phishing-resistant login
- TOTP: time-based one-time codes for 2FA
- Magic Links: one-click passwordless login by URL
- Autologin: tokenized login from webhooks and admin actions
Commerce & Credits
- Credits: balance-and-expenditure system with expirations
- LemonSqueezy & Spiffy: checkout that provisions members
Learning
- Sushi LMS: a native, first-class LMS inside the platform
- Cohorts: cohort groups with shared start dates
- LearnDash, LifterLMS, Sensei, LearnPress integrations
Engagement & Community
- Directory: member directory with per-field privacy
- Group Accounts: seats and sub-accounts for teams
- Pageviews: analytics with simple, duration, heartbeat modes
- BuddyPress & bbPress community integrations
Content, Delivery & Forms
- Content Dripping: release posts and pages on a schedule tied to membership tenure
- Secure Files: protected delivery via S3 / Bunny.net
- Form Builder: drag-and-drop, submissions apply tags
Automation & Developer Surface
- Webhooks: first-class inbound and outbound system
- n8n: automation platform integration
- MCP Server: exposes tools to AI agents
Security
- Hardening: ~30 toggleable controls and security headers
- Multiple Login Limiting: blocks account sharing by watching how many locations an account logs in from
- Login & error logs: every sign-in and failure recorded, surfacing brute-force and credential-stuffing patterns
And more inside the platform.
Plus a wide third-party integration stack
Page-builders, commerce, community, events, automation, and meetings, all auto-detected with nothing to configure by hand.
The agency story
Build once, run against multiple CRMs
You build a client’s membership site once. Access rules, levels, tags, and automations live in the build, not in a CRM. The same build runs identically against Keap, HighLevel, or no CRM at all, and when a client changes CRMs, the site does not change, only the connection.
- Client moves to a new CRM, the build moves with them
- No Keap or HighLevel code to maintain per client
- Launches standalone, so a client without a CRM still goes live
- One implementation playbook your team runs on every project
Own your platform
Your membership site, your access rules, and your features: no matter which CRM you connect
The Torii engine puts your WordPress site in charge: the CRM becomes a connection you can change or drop. License Memberium and run it on your WordPress, with any CRM or none.