Slack
The public invite page Slack never shipped
Slack does have a shareable invite link. It expires after 30 days, stops working after 400 people, and asks nobody a single question on the way in. Put an Inviter page in front of it: one URL that never dies, applications you actually read, and a fresh Slack link issued behind the scenes.
The Slack invite problem
Your invite link has an expiry date and a body count.
Slack was built for companies onboarding employees, so its invite link is sized for that job: 30 days, 400 uses, then it is dead and every README badge and conference slide pointing at it is dead too. Renewing means an owner or admin digging through Workspace settings, and the replacement link screens exactly as carefully as the last one did, which is to say not at all. That gap is why Slackin existed — and its death left the gap open again.
- priority_high Each invite link is good for 400 people and 30 days. Public communities burn through both.
- priority_high When the link dies, so does every README badge, blog post, and slide that ever carried it.
- priority_high Open-domain join is not screening. It is a string match on an email suffix.
- priority_high Slackin has been unmaintained for years. A fork is not a dependency, it is a weekend chore forever.
How it works
How a Slack invite page works
The Slackin pattern — public page, email application, approval — with nothing to self-host.
- web 01
Publish the workspace page
Put the community at inviter.co/your-slug: what it is for, who belongs in it, and what actually happens in the channels.
- mail 02
Collect email applications
Slack invitations are email-based, so a verified email is the right thing to ask for. Country rules and captcha are there when you need them.
- how_to_reg 03
Approve, then bring them in
Work through applications in the dashboard instead of fielding “hey, can I join?” DMs from strangers on LinkedIn.
Features
A Slackin alternative that is still maintained
What former Slackin operators actually need in 2026.
- link
A public URL for a private product
Slack gives a community no front page. This is it: stable, branded, and safe to put in a README that outlives your invite link.
- mail
Verified email, which Slack needs anyway
Workspace invitations go to an email address. Verify it on the way in and the invite step stops bouncing off typos.
- rule
Applications instead of open-domain
Ask questions and approve individuals, rather than admitting an entire email domain and finding out later.
- public
Country allow and deny rules
For workspaces with chapter boundaries, export restrictions, or a region you simply cannot support yet.
- shield
Captcha on the form
reCAPTCHA, hCaptcha, or Cloudflare Turnstile — the check the original Slackin email box never had.
- event
Events for professional communities
Charge for the workshop, keep RSVPs on the same page as the join flow, and settle through Stripe.
Your community lives somewhere else too?
Discord invite pages
Telegram invite pages
WhatsApp invite pagesExamples
Slack communities on Inviter
Slack workspaces already running a public application page.
FAQ
Questions, answered
Not in any dependable way. Some plans offer shareable invite links, but they can expire or be turned off, and everything else is an admin invitation or an open-domain rule. There is no discord.gg equivalent you can post once and forget, which is exactly why Slack communities keep building invite pages.
Give your Slack workspace a front door
The Slackin pattern, hosted and maintained. Free to start; Pro is $19.99/month when you outgrow it.