First commit 29 May 2026 · five-module platform in production 2 July 2026
The verification queue — identity and background check status across the caregiver base, red flags surfaced first.
What it does
Capabilities
Users — search, inspect, deactivate, assign or revoke plans, and extend entitlement windows.
Verifications — identity and background check status for every caregiver, filtered by verified, needs review and red flags.
Plans — full CRUD over the subscription catalogue, including Stripe price IDs and active subscriber lists.
Courses and bundles — create, price, build curriculum, preview, publish and manage enrollees.
Events and marketplace — moderation and management of listings across both modules.
Notifications, error logs and payment settings — including masked Stripe credentials, a mode toggle and a test-connection button.
How people use it
The journeys it was designed around
An administratorWork the verification queue on a Monday morning
Opens Verifications and sees four counters: total, verified, needs review, red flags.
Filters to red flags first — the queue is ordered by what requires a decision, not by date.
Opens a caregiver to see identity verification and background check status side by side with their profile.
Approves, or deactivates the account — a soft deactivation that removes them from public search and blocks sign-in while preserving their history.
An administratorAnswer “why did this user see an error?”
Opens Error Logs, which records client-side failures against the account that hit them.
Cross-references the user record: role, plan, entitlement window, household membership.
Checks Notifications to see what the platform intended to send that user and whether it was delivered or skipped.
How it is built
Implementation and the rules real users find
Under the hood
Twenty-three admin routes sit behind a single guard that checks the admin role against the database, not against a claim in a token.
The same guard enforces soft deactivation everywhere, so a deactivated admin loses access by the same mechanism as a deactivated parent.
Notification types and their email records are data, so what the platform sends can be inspected and changed without a deploy.
An audit log table records administrative actions.
Error reporting writes user-facing failures to a table rather than only to a console nobody is watching.
The rules real users find
Stripe secrets are masked in the interface and never returned to the browser in full — the test-connection action runs server-side.
Admin invitations are their own table with acceptance handled by a SECURITY DEFINER function, so granting admin access never requires loosening a policy.
Because email was parked, admin and staff invitations are copy-link and remain fully functional without SMTP.
The screens
Taken from the live product
Click any shot to enlarge.
Marketplace moderation from the admin console.Course management — status, enrolments and the editor.
The rest of the platform
All 5 modules
These were built on one schema and one permission model, which is the only reason all 5 of them could ship together.
SigmaticAI is led by Ketan Khamgaonkar — an IIT Roorkee M.Tech who went on to PhD research at IIT Bombay before spending four years building AI automation, agentic systems and full web and mobile products. On every project you talk to the person writing the code.
No pitch deck. Tell us what you are trying to ship and we will tell you the fastest honest path to live — including if that path is smaller than you thought.