Your community lives somewhere else. MyFenrir stands in front of it—confirming identity, access and intent before anyone reaches the real room.
Explore MyFenrir by intent. Start with what the system does. Open the procedure only when you need it—or switch reading altitude entirely.
A verified identity gives every later access decision a stable person to attach to—without asking members to create another password.
Community access remains attached to a durable Frisky account identity rather than a temporary browser session.
Identity is resolved at sign-in and connected to the community gate data plane.
The gate evaluates entitlement before generating an invite. The protected group never becomes the place where payment is sorted out.
Access tiers and community-specific rules determine the outcome.
The real group link stays hidden. Only a member who passes the gate receives the final handoff.
One clear result: you are in, you need action, or your access needs review.
Rules appear at the moment they matter, attached to the community being entered.
Acceptance becomes part of the access record instead of an unread pinned post.
Automation handles the obvious. Humans keep authority over the meaningful edge cases.
Profile review, moderation actions, access tiers and decision history.
The member should not learn your infrastructure. They should feel a clear threshold, a fair decision, and a quiet welcome.
MyFenrir keeps the complexity on the side of the system. A person arrives with a link. The gate gathers only what the decision requires. The destination stays private until the moment it is safe to reveal it.
One branded entry point. No app hunt, no dead-end documentation, no invitation forwarded into the open.
Apple, Google or Microsoft confirms identity. No new password, no second account to forget.
Entitlement, rules, Telegram status and invite safety resolve behind the surface.
A safe, single-use handoff to the protected group. The gate recedes.
A gate is not a spinner. It is a set of explicit decisions with an outcome the reader can understand.
That clarity is part of trust. “You’re in” is different from “we need one more thing” and different again from “an owner will review this.” MyFenrir gives each state its own language.
access.grantedIdentity and entitlement are confirmed. The protected destination can be handed over safely.
access.action_requiredA rule, payment or provider step needs the member’s attention before access can continue.
access.needs_reviewThe system keeps the edge case visible and routes it to a human with context intact.
The owner gets one calm place to see what the gate is deciding—and where a human voice is still needed.
Review profiles, set access tiers, clean up chat, ban when necessary. The point is not to replace judgment. It is to keep judgment from being buried under repetitive work.
The system is only trustworthy if its boundaries are legible to the people who depend on it.
These are not marketing promises. They are design constraints carried through the Bridge, Community Gate and the private destination beyond them.
The protected group never becomes a public index. Access is earned at the threshold and invitations stay controlled.
A real account, not a disposable browser session, anchors the decisions made across the community journey.
Automation handles repeatable checks. Ambiguity stays visible, reviewable and owned by the person responsible for the room.
MyFenrir owns the admin shell and entitlement truth. Fenrir Gatekeeper owns the Telegram runtime: waiting room, mute-on-join, welcome card, Mini App verification and one-time invite. Bot OS curates the blueprint and ships the secrets.
botType: communitygates: turnstile · oauth · rules · vibeinvite_ttl: 300swebhook: /api/telegram/webhookA new member arrives in the waiting room muted. The bot presents the community promise and one obvious next action: Verify Now.
Turnstile limits automation. OAuth establishes identity. Rules make the agreement explicit. Vibe review protects the room’s character.
After the checks pass, the Worker consumes the decision and issues a single-use Telegram invite with a five-minute lifetime.
MyFenrir → brand, membership review, Stars entitlement UI, readiness.
Fenrir Gatekeeper Worker → Telegram runtime, waiting room, Mini App, invite consumption.
Frisky Bot OS → community blueprint curator, export and Infisical deployment secrets.
D1 + Stars webhook → entitlement truth. The bot records bot identity; it never becomes the billing database.
This is not one explainer. It is the living map of the product: identity, domains, Telegram locks, workspaces, billing, community review, integrations and the launch gates that keep production honest.
The Bridge is a checkpoint, not a destination. It resolves identity and access, then disappears from the member's path.