Home / Work / KinglyVault

Online education and membership

A learning platform that connects to the AI system on each member's own computer.

A membership platform for AI courses, tools and community that links safely to each member's own InfiniBot, with no network ports to open.

Visit kinglyvault.com Build something like this

Three launch path options on the KinglyVault site

Who it is for: People learning to build with AI tools who want lessons, tools, community and billing in one account.
The problem: A course library alone was not enough. Members needed the AI work to happen on their own systems, and a website normally cannot reach a home computer safely.
What they get: One membership for courses, tools and community, plus a linked connection to the member's own InfiniBot, with no network settings to open up.

116Tools a member's AI can use, within limits

253Per-row access rules written

183Tracked changes to the database

36Small server programs on the database platform

10Small server programs on the web host

The challenge

KinglyVault teaches people to build with AI tools. A course library on its own was not enough. Members needed one place for lessons, tools, templates, community and billing, and they needed the AI work to happen on their own systems, not only in a demo inside a web page.

That created two hard engineering problems. A website has to reach an AI agent running on a member's own computer, often behind a home router, a corporate VPN or a private network, without asking that member to open a port. And a web community has to stay in step with an existing Discord server without creating a second moderation problem.

The system

KinglyVault is a web app hosted on Netlify. Clerk handles sign-in, Supabase holds the database and stored files, and Whop handles checkout and membership status. Membership plans (Free, Starter, CEO and VIP) gate features through one plan catalog in the app.

The platform has three layers around that core.

Learning and member tools. Courses, chapters and lessons with progress tracking, certificates, a launch path of daily missions, a prompt library, an agent vault, AI tools, and an admin console for running the catalog. Gamification sits across this: points, streaks, a leaderboard and rewards.

InfiniBot Connect. A member's own InfiniBot (desktop, cloud or self-hosted) keeps an outgoing connection open to a relay, a go-between on our platform. KinglyVault queues a request, the member's machine pulls it, verifies a signed envelope, and passes it to its local gateway under that gateway's own tool policy. No inbound port or tunnel is involved. From KinglyVault, a linked member can chat with their agents, start coding agents and open pages in their InfiniBot interface.

KinglyVault MCP server. A second connector opens the platform to AI agents through a standard called the Model Context Protocol (MCP), so a member's agent can read and act on that member's own KinglyVault data within the scopes they granted.

Community and Discord sync. A scheduled job checks mapped Discord channels for new messages, while each new KinglyVault post is sent out automatically to its matching channel. Nothing depends on a desktop process or a held-open Discord connection.

Outcomes

The platform is live at kinglyvault.com, with public plans listed on the site.
36 edge functions and 10 Netlify functions (small server programs) are in the main code, counted from the repository.
183 database migrations (tracked database changes) are in the main code, counted from the repository.
116 MCP tools are defined in the server, counted from the repository.
A member can link a machine behind a home router or a VPN with no inbound port, because the connection always starts from their side.

We have left out member counts and revenue. Neither is published here.

Step by step

How KinglyVault works, step by step

The clever part of KinglyVault is how a website reaches an AI system on a member's own computer. This follows one request. The member's machine always makes the first move, so nothing outside can knock on its door.

The member joins and picks a plan
What happens
The member signs in and chooses Free, Starter, CEO or VIP. Checkout runs through Whop, which reports membership changes back to the platform.
Who or what does it
The member, with Clerk for sign-in and Whop for payment.
Why it matters
One list of plans decides what each member can open, so access stays consistent across the site.
The member learns and follows missions
What happens
Members work through courses, chapters and lessons, or a launch path of daily missions on one of three tracks: web agency, automation or content. Progress, points and streaks are saved.
Who or what does it
The member, on the KinglyVault site.
Why it matters
People see what to do next each day rather than facing a pile of videos.
The member links their own AI system
What happens
The member approves a link to their own InfiniBot, on desktop, cloud or self-hosted. A short-lived pairing code does this once, and a returning computer does not have to pair again.
Who or what does it
The member, approving on their own device.
Why it matters
Setup takes no router changes, even behind a home router or a company VPN.
Their computer asks for work
What happens
The member's InfiniBot keeps an outgoing connection open to a relay on our platform, asking whether anything is waiting for it.
Who or what does it
The member's InfiniBot and the relay.
Why it matters
Because the connection goes out, no inbound port or tunnel is needed. That removes a common security risk.
The website leaves a request
What happens
When the member chats from KinglyVault, the site puts a signed request in a queue. The member's machine picks it up and checks the signature.
Who or what does it
The KinglyVault site, then the member's machine.
Why it matters
A linked member can talk to their agents from the site, while the request stays verifiable.
Their own rules decide
What happens
The request passes to the local InfiniBot under that InfiniBot's own tool rules. The member's gateway token never leaves their machine. Moving up from read to write or admin access takes the member's explicit approval.
Who or what does it
The member's InfiniBot, under limits the member set.
Why it matters
The member stays in charge. Requests go into an audit log the member can read, and either side can revoke the link.
Community stays in step with Discord
What happens
A scheduler checks mapped Discord channels, and new KinglyVault posts are sent out by webhook. Live mentions such as @everyone are defused. This bridge is built and deployed behind a switch, and at the last recorded check it ran in staff mode with a test channel only.
Who or what does it
Automated jobs inside Supabase, the platform's database service.
Why it matters
When opened up, it can spare the team a second moderation job, because nothing relies on a desktop app staying on.

Architecture

How the system fits together

01 / 07 The member's side

Member browserWhere the member learns and chats.→ KinglyVault app → Clerk · sign-in
Member's InfiniBotRuns on desktop, cloud or self-hosted.→ InfiniBot relay · outbound long-poll → KinglyVault MCP · scoped token

02 / 07 The website

KinglyVault appThe main site, hosted on Netlify.→ Supabase Postgres → InfiniBot relay · queued request

03 / 07 Sign-in

ClerkHandles secure sign-in.

04 / 07 Stored records

Supabase PostgresStores data, with rules on who sees each row.

05 / 07 Billing

WhopTakes payment and reports membership changes.→ Supabase Postgres · webhook

06 / 07 Connectors on our platform

InfiniBot relayHolds signed requests until the member's machine collects them.
KinglyVault MCPLets a member's AI use 116 tools within granted limits.→ Supabase Postgres
Discord bridgeCopies messages both ways, on a schedule.→ Supabase Postgres → Discord server · REST and webhook

07 / 07 Community

Discord serverThe existing community server.

The public page describing the InfiniBot workspace members get.

Key features

Course platform with chapters, lessons, progress, certificates and admin tooling
Launch paths with daily missions, built around three tracks: web agency, automation and content
Free, Starter, CEO and VIP plans enforced through one plan catalog, with checkout through Whop
InfiniBot Connect: link a member's own AI system with a device approval, with no open ports
Device fingerprint reuse so a returning computer does not have to pair again
AI side panel on member pages, with lessons a member can work through with their own InfiniBot
MCP server with 116 tools across read, member, write and admin groups
Two-way Community and Discord message sync with mirrored edits and deletes
Discord account linking shared across community and role features
Proof review queue that grants a Discord role after an admin approves it

Delivery

We started in April 2026. Commit history on the main branch shows 384 commits to 30 October 2026, with the heaviest periods in June and July (the platform build) and October (190 commits, mostly the InfiniBot Connect work, the upgrade system and Discord sync).

Larger features shipped from their own branches with a written security or feature document alongside the code, such as the threat model for InfiniBot Connect. The repository holds 79 test files. On-off switches let us release code before opening a feature to members. The Discord bridge has off, staff and all modes for this reason.

Security & infrastructure

Per-row access rules. The database has row-level security, which controls who can see each row. Our change history holds 161 statements that turn it on and 253 written rules. The relay tables go further, so only server code can touch them.
Relay design. Pairing codes are short-lived. They and device secrets are stored only in scrambled form. Relay tokens are encrypted. The member's gateway token never leaves their machine. Requests are scoped, signed, rate limited and written to an audit log that the member can read on both sides. A link can be revoked from either side.
Scoped consent. Access is split into scopes such as read, write and admin. Moving up a scope takes an explicit approval from the member, not a database edit.
Discord hardening. Outbound posts carry no live mentions, @everyone and @here are defused, role and user mention syntax is neutralized, message length is capped, and each member is rate limited. Loop prevention stops the bridge from ingesting its own posts. A Discord ban on a linked member carries into KinglyVault, and the bridge never bans anyone on Discord.
Sensitive uploads. Proof files live in a private bucket with no storage policies. Viewers get short-lived signed URLs, the server checks file type and hash, and files are deleted on a retention schedule. Account numbers are never stored in full.
Hosting. Netlify for the front end, Supabase for data and edge functions, Clerk for identity, Whop for payments.

What's next or limits

The Discord bridge is built and deployed behind its flag. At the last recorded check it ran in staff mode, with a test channel only, and had not been opened to all channels. Discord sign-in linking also waits on a configuration step, so account linking currently uses a one-time code sent by the bot.

Built with

The tools behind it

For technical readers, here is what it runs on. Tap a name to highlight it. The words explained below appear across this page.

What these words mean

Single-page app: A website that behaves like an app, updating without full page reloads.
Relay: A go-between that holds messages until the other side collects them.
Outbound long-poll: A computer repeatedly asking a server, "anything for me?", so nothing has to reach in.
MCP (Model Context Protocol): A standard way for AI agents to use outside tools and data.
Row-level security: Database rules that control who can see each individual row.
Edge function: A small program that runs on the hosting provider when called.
Repository: The stored, versioned code of a project.
NAT and VPN: Common network setups that stop outside connections reaching a computer directly.