Nubase

Nubase's pitch is narrow and sharp: your coding agent writes the code, Nubase gives that code somewhere real to live. The eight modules are chosen well. Database gives each project an isolated PostgreSQL instance with a PostgREST-compatible REST API and Row-Level Security executed against JWT claims, which means the RLS policies your agent writes actually gate requests rather than sitting inert. Auth is deliberately Supabase-compatible, including drop-in support for Supabase client SDKs, so an agent trained on that pattern can wire email, OAuth, magic links, MFA/TOTP, OTP and anonymous sign-in without you hand-holding it. Storage is S3- and R2-compatible with public and private buckets, signed URLs and policy-aware access, and Assets publishes the generated frontend to a public CDN at /assets/v1, which removes the usual step of bolting on Vercel or Netlify just to see the app online. The parts that are genuinely differentiated are Functions, AI Gateway, Memory and cron. Functions run at /functions/v1 with per-function secrets, logs, verify_jwt and a choice of local or Cloudflare Workers runtime, so backend logic written by an agent deploys without a separate serverless account. The AI Gateway is a single OpenAI- and Anthropic-compatible endpoint with per-project keys and usage tracking, which keeps model routing and spend visible per project rather than smeared across one shared org key. Memory is the strongest piece: a mem0-compatible REST API where facts are extracted, embedded and recalled through a hybrid retrieval engine fusing vectors, BM25 and entity boosts, with audit history and pluggable OpenAI, Anthropic or OpenAI-compatible providers. The vendor's June 2026 blog argues explicitly that prompt stuffing is not memory — and architecturally they back that up, since memory here is a first-class tenant-scoped primitive rather than a script wrapped around a vector store. cron closes the loop by letting scheduled jobs invoke an edge function or a database function on a crontab, run by the control plane with run history, which is what turns a demo into an app that keeps working unattended. Where it does not fit: Nubase is self-hosted, so someone on your team owns Docker, upgrades and backups. The captured documentation describes protocols and compatibility rather than a wide catalog of named third-party SaaS connectors, so if your project depends on a long list of prebuilt integrations, verify coverage before committing. Model and embedding spend flows through your own provider keys via the AI Gateway, so cost predictability depends on how you configure routing and usage caps. And the mental model — apikey JWT for tenant and role, a second bearer token for the end user — is simple once internalized but is still a model you have to learn. For agent-driven developers who want protocol compatibility and no per-project billing, that learning curve is cheap. For teams that need a managed control plane and an ops-free footprint, it is not.