§ 00 / CLIKKIN
Clikkin is a community platform for serious operators.
Turn your existing audience into recurring revenue — with branded iOS and Android apps from $100 a month, regional pricing keyed to your country, and a built-in coin economy.
§ 02 / EARNINGS ESTIMATE
What could your existing audience earn?
A quick calculator. No signup. We don't capture what you type.
§ 03 / FOR FREE COMMUNITIES
If you run a community on WhatsApp, Telegram, Facebook, Discord, or YouTube — you already have the hard part. You have an audience that trusts you.
What you're missing is a clean way to charge them.
- CHARGE IN YOUR CURRENCY
- INR direct to your Indian bank via Razorpay Route. USD via Stripe Connect for the US, EU, and the rest of the world. No FX markup, no 7–8% PayPal tax on international transfers.
- PRICE FOR YOUR AUDIENCE
- Pro starts at ₹830 a month in India ($10), scaling up to $100 a month in the US — same features at every tier. Your subscription tier follows your verified country.
- FREE TIER + PAID TIER
- Keep most of your content open. Gate the premium tier with a paid badge. Members who don't pay still see your space and can engage on free posts.
- LAUNCH SUPPORT INCLUDED
- We can't move your members from WhatsApp for you — no platform can; the source APIs don't expose it. But once you launch your Clikkin space, we'll give you tailored announcement scripts, QR codes for member invites, and a 30-day migration dashboard.
§ 04 / FOR SWITCHERS
If you're already paying a community platform, you know the trade-offs.
Branded apps cost $1,417–$2,500 a month. Transaction fees stack to 8–14% of revenue at 500+ paying members. The best features are behind higher tiers.
- BRANDED APPS
- Plus starts at $100 a month (Tier C) to $1,000 a month (Tier A). Mighty Pro Basic is $1,417 a month. Circle Plus is roughly $2,500. The branded-app tier is the same product on iOS and Android, published under your own developer accounts.
- NO PER-MEMBER FEES
- Pay for the tier, not for headcount.
- REGIONAL PRICING
- If your audience is in India, Brazil, or South Africa, the platform price scales with your country — not the US default.
- DEPTH OF CUSTOMISATION
- Badges as sole authorisation primitive, sub-spaces with their own structure, programmable server-side actions (WASM), five space templates.
§ 05 / FOR NEW COMMUNITIES
Choose a template, customise the badges, set your monthly tier price, and launch.
Community
For paid memberships, masterminds, and ongoing learning communities.
Brand
For public-figure spaces and superfan communities.
Organisation
For companies, schools, and non-profits running internal or member-facing communities.
Fan Club
For artists, athletes, and entertainers with paid supporter tiers.
Academy
For cohort-based courses and self-paced learning communities.
§ 06 / SPACES
A space is a self-contained social network.
Each space has its own badges, members, posts, and feed structure. Spaces can be public, private, or mixed. The owner sets the rules, the badges, the membership tiers, and the pricing.
§ 07 / THE COIN ECONOMY
The platform's built-in micropayment primitive.
$1 USD = 1,000 coins, permanent peg. All write actions cost coins; reads are free. Members get a monthly subscription allotment that resets each cycle. Larger allotments are available via coin vaults ($5–$5,000+ with SOFR-bonus tiers). Space operators can charge coins for premium posts, paid roles, tipping, sponsored actions, and store purchases.
Coins are a closed-loop platform economy, not a cryptocurrency. They are not on-chain, not transferable to external wallets, and not redeemable as fiat. Plus and Enclave operators can convert marketplace revenue to fiat through Stripe Connect (US/EU/RoW) or Razorpay Route (India — INR direct to your Indian bank).
§ 08 / BADGES
The platform's single authorisation primitive.
Roles, permissions, verification status, and a member's standing in a community all live on badges issued by the space. Designed once by the space owner, issued to members, revocable by the issuer, and held in the member's device-side badge locker.
There are no separate permission matrices and no hidden admin overrides — every permission a member has comes from a badge they hold. Composable, hierarchical, and extensible with add-on slots that each contribute exactly one additive permission.
§ 09 / HOW IT'S BUILT
Five architectural choices and one boundary we are explicit about.
- ON-DEVICE IDENTITY
- Identity fields (legal name, date of birth, nationality, phone) live in a hardware-encrypted Secure Vault on the member's device. Clikkin's servers store HMAC hashes and risk scores — never the underlying values.
- SPACE-OWNED KEYS
- Each space's private content is encrypted under keys held only by that space's admins. Clikkin's servers store ciphertext only.
- TIERED QUERIES
- Spaces ask "is this member over 18?" and receive a boolean — never the date of birth.
- E2E MESSAGING
- Messaging uses MLS (RFC 9420). Clikkin's servers store opaque ciphertext only.
- EXPORTABLE
- Members and operators can export their content, members, badges, and wallet recovery phrase at any time.
- THE DIDIT BOUNDARY
- Identity verification is processed by Didit, our KYC partner, for up to 72 hours during Passport activation. Raw documents do not persist on Didit's servers beyond that window per the Data Processing Agreement.
§ 10 / WHAT YOU'D PAY
Pro, Plus, and Enclave — your pricing in your country.
Sold by Clikkin LLC (Wyoming, USA) · Change region in the nav bar.
§ 11 / TRUST AND TRANSPARENCY
Clikkin is a closed-source platform on our own infrastructure.
We publish what we can verify and we are explicit about what we don't yet do.
- QUARTERLY DISCLOSURES
- Service uptime, government data requests received, account actions under the platform-policy hard-line offence list, and P1/P2 incident reports — published every quarter on the trust page.
- REPRODUCIBLE BUILDS
- Our Android client builds are deterministic and verifiable against the corresponding commit hash. Verifier recipe published.
- RESPONSIBLE DISCLOSURE
- security@clikkin.com — acknowledgement within 7 days, public credit on resolution.
- WHAT WE DON'T DO YET
- Third-party security audit: planned, not yet booked (pre-revenue). Paid bug bounty: not affordable pre-revenue. Federation / self-hosting: not in roadmap.