Kapnet helps private groups run access, roles, perks, moderation, credentials, workflows, and shared service capacity as structured state instead of scattered admin labor.
Kapnet is not a decentralized compute marketplace. It is a member-governed operational substrate where groups pool software, workflows, hardware, rooms, agents, credentials, perks, and service capacity under structured trust-state.
Every room is gated. Membership state, roles, permissions, and sanctions live in an auditable substrate — not scattered across chat logs and spreadsheet tabs.
Discord is the interface. Kapnet is the source of truth. Membership, permissions, and reputation survive platform changes because they live outside any one app.
Coordination disappears into chat history in a normal group. Kapnet turns roles into capabilities, perks into claimable objects, and moderation into a structured queue with audit trails.
Your members use whatever they prefer — Telegram, Discord, Matrix, Nostr, or the native LLobby interface. The state stays in Kapnet; the chat app is just the window.
The chat app is only the interface. Kapnet holds the membership state — gated rooms, role sync, perk claims, moderation queues, reputation, and auditable records that survive any platform change.
Access is automated by membership tier, invitation, or claim. No invite links floating around, no manual vetting.
Charge for room entry, tier upgrades, or perks. Stripe and Lightning payments built in. Access grants are cryptographic tokens, not database flags.
Assign roles in Kapnet; they propagate to every bridged platform automatically. Revoke a member once; they lose access everywhere.
Members unlock perks at tier thresholds — study guides, templates, service credits, consulting hours. Perks are claimable objects with expiration and audit.
Flagged messages enter a structured queue. Moderators act with context: previous flags, member history, sanction log. No autonomous bans in v0.
Room activity is summarized by agents you configure. Catch up after absence, get daily digests, or archive community knowledge.
Every role change, sanction, perk claim, and room creation is time-stamped and signed. Export your community's full state at any time — no vendor lock-in.
Your members use their existing platform. Kapnet connects underneath. Bridge development is roadmap-prioritized by member votes.
Discord is the interface. Kapnet is the source of truth. Membership, permissions, perks, sanctions, and reputation should survive platform changes — because they live outside any single app.
Not everyone starts at the top. Each tier unlocks more pool capacity, governance weight, and trust scope. Movement is by contribution and reputation, not payment alone.
Observe, learn, and begin participating.
Run a project room and deploy workflows.
Contribute services, hardware, or capacity to the pool.
Govern infrastructure priorities and approve policy.
Each package is a pre-configured room stack with gates, roles, perks, and moderation tuned for its purpose. Deploy in minutes.
Gated room with tiered access, role sync, perk claims, moderation queue, and agent summaries. The core building block.
Time-boxed learning cohorts with progress gates, facilitator roles, assignment tracking, and graduation perks.
Private group for creators with content gates, early-access perks, collaboration rooms, and audience bridges.
Peer group for founders with intro-verified access, investor-ready templates, shared service credits, and accountability workflows.
Member directory, CPD tracking, event coordination, committee rooms, and credential-verified gates.
Study groups with curriculum tracks, quiz gates, mentor roles, Nostr-published credentials, and on-chain attestation.
Local-first community helpdesk with topic routing, verified-resident gates, bilingual moderation, and service-provider directory.
Complete community operating system with KOR governance, TXXM-shaped events, role/capability gates, perk objects, moderation transitions, and bridge adapters. For groups ready to run their coordination on structured state.
Kapnet is infrastructure, not a financial product. There is no token, no passive income claim, and no platform lock-in. Every commitment is stated plainly.
Not a token sale. Not a cryptocurrency. Membership is a service subscription.
Not investment advice. No projected returns. Contributions are voluntary.
Not passive income. Pool earnings are shared among active operators per settled rules.
No platform lock-in. Export your full community state at any time.
No autonomous bans in v0. All serious sanctions require human approval.
Human approval required for bans and role revocations. Appeals are manual.
Exportable records. Every action is timestamped and available for download.
Client-defined policies. You set your own gates, roles, and moderation rules.
Privacy-minimized identity. Join with the minimum identity required for your tier.
No data mining. Your community's conversations and membership data belong to your community.
KOR state, TXXM-shaped events, role/capability gates, perk objects, moderation transitions, and bridge adapters make the system portable across chat platforms. Membership state is not locked to any one interface — it lives in a structured, auditable substrate that survives platform changes, bans, and migrations.
Kapnet makes membership operational: rooms become governed spaces, perks become claimable objects, roles become capabilities, and coordination stops disappearing into chat history.