I kept rebuilding the same backend for every side project, so I built Kroxt

Adepoju Oluwatobi — Sat, 15 Aug 2026 19:16:07 +0000

The problem

[1-2 paragraphs: every project needs auth, a database, storage, email —
you've built this five times, here's why that got old]

What Kroxt does

Multi-tenant auth with strict session revocation and brute-force protection
Schema-validated MongoDB collections, auto REST CRUD
File storage + CDN
Serverless functions (JS VM, DB-hook or cron triggered)
Realtime WebSocket channels
Paystack payments & subscriptions

What using it looks like

import Kroxt from "@kroxt/baas-sdk";

const baas = new Kroxt({ projectId: "your_project_id", apiKey: "your_api_key" });

const results = await baas
  .collection<UserProfile>("profiles")
  .where("role", "equals", "developer")
  .where("active", "equals", true)
  .orderBy("createdAt", "desc")
  .limit(5)
  .get();

Where it's at right now

This is a developer preview — auth, database, SDKs, functions, and
realtime are live. Webhooks are in progress; team workspaces and usage
analytics are next.

What I need from you

If you've used Firebase, Supabase, or Appwrite, I'd love to know:
does the auth/rules model make sense? What's the first thing you'd
try to break? Free tier is live, no card needed — try it and roast it
in the comments.