LM Gate – Auth and access-control gateway for self-hosted LLM back ends
Single component replaces nginx + auth + monitoring for exposed Ollama instances.
A BaaS (Backend-as-a-Service) solution for web applications, inspired by the flexible nature of triplestores. Featuring real-time collaboration and serverless authorization 🔐
Implements a graph-first BaaS with live subscriptions (there's even a subscribeToQuery entry) and serverless auth hooks so clients can get streaming updates on linked-data. It’s a focused alternative to generic BaaS offerings for teams who actually need RDF-style data and collaborative syncing. Active commits and docs are promising, but community traction and integration stories will determine whether it escapes niche status.
Frontend developers building SPAs, indie devs and teams who want a self-hosted BaaS with auth and realtime, projects avoiding managed services
Single component replaces nginx + auth + monitoring for exposed Ollama instances.
Auto-generated Row-Level Security plus a three-schema model (document / managed / unmanaged) is the concrete feature that makes this more than yet another BaaS rewrite — you can prototype like NoSQL then flip to managed tables with permission tables and RLS without hand-writing policies. It bundles auth, permission-aware file storage, messaging and embeddings storage which is useful for ML workflows, but it's entering a crowded field (Supabase/Hasura/Appwrite) and would benefit from clearer migration stories, performance numbers, and a hosted roadmap.
TDD-first auto-fix approach writes failing tests before generating patches, not just patching blindly.
Enterprise auth for MCP when the protocol itself has no security layer.
Four-agent pipeline from Sentry crash to PR, but human approval still required.
GitHub Gists as a database means zero backend costs and full portability.