Auth Plugin vs Thenty: Comparing Two Framer Membership Plugins

• Thenty is a native Framer plugin for membership sites: sign-up, login, gated content, and Stripe payments bundled together.
• Auth Plugin is also native to Framer, but stays focused on authentication and gating, without payments or a member CRM built in.
• Thenty's Launch tier is $24/month billed annually for up to 1,000 users, plus a 1.5% transaction fee. Auth Plugin's comparable tier is $19/month with no transaction fee.
• Thenty supports password and Google login. Auth Plugin adds GitHub OAuth, magic links, and OTP on top of both.

Thenty and Auth Plugin both live directly inside the Framer editor, no external script embed required, which puts them closer together than most comparisons in this space. Where they split is scope: Thenty is a membership-and-payments product with auth attached, Auth Plugin is an auth product that leaves payments to whatever tool a site already uses. This covers both, honestly.

Thenty markets itself as a way to "build, launch, and scale" a Framer site with user accounts, subscriptions, and protected content, all in one plugin. Sign-up, login, Stripe checkout, a CRM-style member dashboard, and gated sections come packaged together.

Auth Plugin covers the authentication half of that list, sign-up, login, sessions, gated pages, and profiles, and stops there. There's no built-in payments layer, no member CRM. If a site needs to sell subscriptions, that runs through Stripe or another checkout tool directly, connected to the site separately from login.

The practical difference: Thenty assumes payments are part of the build from day one. Auth Plugin assumes they might not be, or that they're better handled by a dedicated payments tool the site is already using.

Thenty works as a drag-and-drop plugin inside Framer, with pre-built templates, sections, and blocks for sign-up, login, and member areas. Per Thenty's own FAQ, no coding is required for any of it. Getting a paid membership live also means connecting Stripe, since Thenty's subscriptions and one-time purchases route through it.

Free features (gating, Google SSO, basic auth) work without a Stripe connection. Paid tiers and paid content require it, since that's where Thenty's checkout and transaction fee come into play.

Auth Plugin's components drop into a Framer page the same way, no code, styled to match the site. The difference is what's connected behind them: nothing external is required to get login working. Sign In Form, Sign Up Form, and the rest of the 13 components function immediately, and Protected Pages locks down whichever pages need to be members-only.

If a site later adds paid tiers, that's where Auth Plugin's advanced access control (Pro and Scale) comes in, gating content by role or plan, while payments themselves still run through whatever checkout the site connects separately.

Not based on what Thenty publishes: its documented auth methods are password-based sign-up and Google SSO, with no mention of magic links, OTP, or GitHub OAuth. For a site that wants to skip passwords entirely, that's a real gap.

Auth Plugin includes magic links and OTP as first-class components, alongside GitHub OAuth as a second social provider beyond Google. If passwordless is a requirement rather than a nice-to-have, that narrows the choice on its own, regardless of the rest of the comparison.

Thenty gates at the page, section, or block level, tied to whichever plan a member is on: free visitors see one version, paying members see another, controlled from inside the plugin's dashboard alongside the CRM data.

Auth Plugin splits gating into two components. Protected Pages locks an entire page behind login, the right call for a full members' area or dashboard. Access Switch shows or hides a specific section within a page that's otherwise public, useful for a preview-then-gate layout where visitors see part of the content before being asked to sign in. Tiered access, free members seeing one thing and paid members another, is handled through advanced access control on the Pro and Scale tiers.

Both approaches land in the same place for a simple free-vs-paid site. Thenty's version is more automatic since plan and content access are already linked; Auth Plugin's is more explicit, two separate components doing two separate jobs, which gives more control over page-level versus section-level gating without needing a plan structure to hang it on.

It's possible, but it isn't instant, mainly because Thenty's member and payment data live inside Thenty's own system. Moving to Auth Plugin means recreating those accounts as Auth Plugin identities and reconnecting whatever payment processor the site uses directly, since Auth Plugin doesn't inherit Thenty's Stripe configuration.

For a site still in early testing with few or no paying members, that's a small job. For a site with an active paying membership already running through Thenty's checkout, it's worth planning the account migration and any downtime around billing before swapping the plugin out, rather than treating it as a drop-in replacement.

Thenty's Launch tier is $24/month billed annually (about $288/year) for up to 1,000 users on one site, with a 1.5% transaction fee and a 14-day trial. Higher tiers, Grow and Scale, exist for larger user counts, though Thenty doesn't publish exact pricing for those beyond Launch. Additional sites are billed separately at $29/month each.

Auth Plugin's Pro tier is $19/month for 1,000 identities across 5 sites, no transaction fee. At $2,000/month in payments moving through a site, Thenty's 1.5% fee adds roughly $30/month, or $360/year, on top of its subscription, a gap that widens as revenue grows. The full pricing breakdown covers Auth Plugin's Basic, Pro, and Scale tiers if the identity count or site count needs to go further.

Thenty fits when:

• Payments are core to the site from launch, and a bundled Stripe integration saves setup time
• A member CRM dashboard (growth stats, exportable member list) is genuinely useful, not just a nice extra
• Zapier, Intercom, or Rewardful integrations are already part of the workflow

Auth Plugin fits when:

• Passwordless login (magic links or OTP) matters, since Thenty doesn't offer it
• Payments aren't part of the site yet, or run through a separate, dedicated tool
• A flat subscription with no transaction fee is worth more than a bundled CRM

Is Thenty a real Framer plugin, or a script embed like some competitors?
It's a native Framer plugin, closer in that sense to Auth Plugin than to script-embed tools like Outseta.

Can I use Auth Plugin and add payments separately?
Yes. Connect Stripe, Lemon Squeezy, or another checkout tool directly, and use Auth Plugin's Protected Pages or advanced access control to gate the content those payments unlock.

Does Thenty support GitHub login?
Not based on its published feature list; Google SSO is the only social login method mentioned alongside standard email/password.

Which one has a lower total cost for a small paid membership?
At 1,000 users and modest monthly revenue, Auth Plugin's flat $19/month tends to stay cheaper than Thenty's subscription plus transaction fee, unless Thenty's CRM and payment bundling are replacing tools the site would otherwise pay for separately.

Do both plugins work without writing any code?
Yes, both are drag-and-drop, no code required for either core setup.

Does Auth Plugin include a member CRM like Thenty's?
No. Auth Plugin's Profile Form, Avatar Component, and Identity Label handle the member-facing side, letting users see and edit their own data, but there's no site-owner-facing CRM dashboard or exportable member list built in.

Can I run Thenty and Auth Plugin on the same Framer site?
Nothing technically prevents installing both, but doing so means two separate auth systems managing accounts on one site, which usually creates more confusion (duplicate sign-ups, mismatched sessions) than it solves. Pick one as the source of truth for logged-in users.

Thenty and Auth Plugin are both genuinely native to Framer, which puts them closer than most matchups in this space. The real decision point is scope: Thenty bundles payments and a member CRM into the plugin itself, at the cost of a transaction fee and a narrower set of login methods. Auth Plugin stays focused on authentication, including passwordless options Thenty doesn't offer, and leaves payments to whatever tool a site already runs. Pick based on whether payments belong inside the auth plugin or somewhere else.