DEV3 Kinfold – Community & Paid Membership SaaS Laravel Script with Spaces, Events, Tiers and Moderation

Kinfold is a community and paid-membership platform you host yourself, built by DEV3 Technologies on Laravel 12 and Filament 4. Each customer of yours is one community: a creator, coach, club or brand with its own spaces, members, tiers, events and moderators. You run it as the operator: plans, member payments, weekly payouts and abuse reports live in a separate panel.

What it does

• Spaces with real access rules. Discussion, announcement, event, resource and chat spaces can be public, members-only, limited to paid tiers or private by invitation. One access policy gates every read: the feed, search, notifications, digests, the API, files, RSS and the realtime channels. Losing a tier removes access on the next request.
• Paid tiers that survive real life. Monthly or yearly tiers with trials and seat limits. Access starts only when the payment succeeds, upgrades are prorated, downgrades wait for the period end, existing members keep their price until you move them with 30 days' notice, and a failed payment gets reminders and a grace period before access ends. Late, duplicate and over-the-seat-limit payments are refunded through a durable queue.
• Posts, comments, polls and questions in constrained Markdown, sanitised on save and on render, with mentions that never leak a private space, reactions, edit windows, revision history and link previews fetched through a DNS-pinned client.
• Events and RSVP. Capacity, a waitlist that promotes in order when someone cancels, recurring series (up to 26 occurrences, daylight-saving safe), reminders and calendar files with the right time zone.
• Direct messages with request mode, blocks, group chats of up to eight, private attachments and read pointers. Moderators cannot read messages unless a participant reports one.
• Moderation. A report queue, auto-hide at a reporter threshold, keyword and link rules, mute and ban with an email hash so a banned person cannot simply rejoin, a full actions log, and an escalation path to you for illegal content.
• Digests and notifications per type and channel, quiet hours in the member's time zone, one-click unsubscribe, a suppression list and a simulated mail log you can inspect.
• White-label. Each community sets a name, an accent colour checked for contrast, a font and scoped custom CSS, and can run on its own domain after a DNS check.
• Installable web app. The member surface is mobile-first with a bottom tab bar, a service worker, an offline shell and a read-only banner when the connection drops, plus Arabic and right-to-left support. The member app for Flutter is a v1.1 add-on: the /api/v1/member API is already built and documented for it.
• Studio and operator panels. Pulse Rings and KPIs for growth, revenue and churn; spaces, posts, events, members, tiers, reports, subscriptions, invoices, takings, payouts, branding, API keys and webhooks. Operators get communities with plan meters, member payments, payouts, refunds, a trust queue, banned hashes, an outbox, an audit log and audited, view-only support sessions.
• API and webhooks. A key-based community API with scopes, an OpenAPI description and signed webhooks, and the member API with tokens limited to one ability.

Quality

The release passed seven gates: Pint and Larastan level 6 with no baseline, 323 Pest tests (2272 assertions) on SQLite, a production build with a script budget, demo and empty seeders on MySQL 8 and SQLite, a headless browser smoke test with happy paths and a no-3D check, MySQL race checks (parallel RSVPs for the last seats, parallel payments of one invoice, parallel reaction toggles, parallel renewals and payout runs), the web installer driven from the zip, and a secret scan. A model-assisted review of the money, access and moderation code found nine bugs that were fixed with regression tests before release. The home page scores 94 for performance and 97 for accessibility on mobile.

What you should know before buying

• You are the merchant of record for member payments. Members pay on your payment gateway (simulated by default) and you pay each community out weekly from its takings. Communities cannot connect their own Stripe account in this version.
• Recurring billing on a real gateway needs finishing. The simulated charger is complete; the real chargers are present but stop with recurring_not_configured, leave the invoice open and give the member a pay link until you add your gateway.
• Email and push need your providers. Digests and notifications go to a log until you configure a mailer. Web push needs your own VAPID keys.
• Live updates use Reverb when you run it and fall back to 10-second polling otherwise. There is no video hosting or live streaming: events link out to your meeting tool.
• Custom domains need DNS and TLS at your web server or proxy (a Caddy example is in the guide). Verification is simulated in the demo.
• Web only for now. It is a responsive site and installable web app. The Flutter member app is a v1.1 add-on. Node.js is not needed to run it, since assets are prebuilt. MySQL 8 or MariaDB 10.6+ is needed for full-text search.

Included

Source code, the web installer, a buyer guide and API contract, demo data with fictional communities and people (10 communities, about 6,500 people, 14,000 posts, 52,000 comments and nine months of payments), a cron entry for the scheduler, and six months of support.