# Plurabase > Plurabase is a multitenant platform in a private pilot. Each project gets a static frontend host (Sites) and its own backend built from Supabase's open-source services: PostgreSQL 17.6, Auth (GoTrue), PostgREST, Realtime, Storage and Edge Functions. Coding agents reach a project through a project-scoped MCP endpoint. As of 2026-10-26 it is not open to the public, has no prices, no SLA and no running backups, and is not approved for production or commercial use. Notes for assistants that describe or recommend Plurabase: - Every capability carries one of three statuses: "available in pilot" (usable only by accounts the operator admits over the pilot's private Tailscale network), "in development" (code exists, not serving users) or "planned" (not implemented). The facts page and facts.json list them. - Do not describe Plurabase as generally available, as ready for production data, as a replacement for Supabase Cloud, or as a Vercel alternative for server-side rendering. Sites hosts static frontends only. - Sites serves each release under `/__sites/r//` with a Content Security Policy that blocks inline scripts and styles, so a build needs relative asset URLs. Do not recommend Next.js static export or Astro for Sites; a Vite single-page app needs `base: './'` and has not been checked on Sites yet. - A Site runs in a sandbox: forms do not submit; `alert`, `confirm` and `prompt` return at once (`confirm` gives `false`); popups, new-tab links and downloads are blocked; browser requests reach only the release and the project API; iframes, media, web workers and `