The story behind Qelos
An AI-first application layer gateway, built so your team never has to rebuild the same backend twice.
Why we built Qelos
Hi, I'm David Meir-Levy, the creator of Qelos. After more than a decade as a Tech Lead and Senior Developer, I kept seeing the same shape every time a team started a new product: months spent building authentication, multi-tenant data, role permissions, audit logs, and an admin panel — before anyone could touch the actual product.
With AI in the mix, that gap got worse. Teams would bolt LLM features on top of an already-fragile backend, where the AI didn't share auth, didn't respect workspace boundaries, and couldn't be audited. The "AI part" lived in a separate world from the rest of the app.
Qelos is our answer: an AI-first application layer gateway. One managed instance exposes a RESTful API, AI agents, authentication, multi-tenant workspaces, permissions, and an events log — all reachable through a unified SDK and per-framework middleware. You stay in your own framework. Qelos plugs in as middleware: the @qelos/integrator-* package for your stack reads the request, attaches the authenticated user, workspace, and SDK client, and lets your handlers focus on application logic.
Your app talks to the same Qelos instance that hosts your admin panel — so data, auth, and AI all stay in sync. You define your data model with blueprints in the admin panel, and CRUD endpoints, permission enforcement, and audit logging are generated for you.
We sell that gateway as a managed, hosted service. You get a tenant; we run it. You ship features.
The Qelos Timeline
Early Career & Foundation
Started in web development, building a strong foundation in JavaScript and Node.js — and noticing the same application-layer plumbing appear in project after project: auth, tenancy, permissions, audit, admin panels.
Technical Leadership
As a Tech Lead across multiple startups and enterprises, I watched teams rebuild the same backends from scratch — and then bolt AI on top as an afterthought, untethered from auth or tenancy.
The Gateway Idea
AI-first products needed something different: a managed application layer where data, auth, permissions, and AI agents share one context — reachable through middleware, not a rewrite.
Qelos Launch
Founded Qelos as an AI-first application layer gateway: one managed instance exposing a RESTful API, AI agents, auth, multi-tenant workspaces, permissions, and an events log through a unified SDK and per-framework middleware.
Managed Tenants & Integrators
Shipping hosted Qelos tenants and @qelos/integrator-* packages so teams can stay in their own framework — Express, Nest, Next, Fastify — and still get a fully managed backend in place by the end of the day.
Core Values
Framework-native
No rewrite. Drop the integrator into your stack and get user, workspace, and SDK on every request.
AI-first by Default
AI agents share the same auth, workspace, and permission context as the rest of your app — not a sidecar.
One Source of Truth
Your app and admin panel talk to the same managed Qelos instance, so data, auth, and AI never drift.
Developer-first
Unified SDK, typed clients, and clean middleware. Your handlers focus on application logic — nothing else.
Get a managed Qelos tenant
Skip the backend rebuild. Spin up a hosted Qelos tenant, drop the integrator into your framework, and ship features by tonight.