Platform target
Supabase.
Use Nift for the static frontend and Supabase for backend capabilities such as Postgres, authentication, storage, realtime data and edge functions.
nift init --target=supabase
nift buildSupabase is primarily backend infrastructure rather than a general static-frontend host. The Nift target therefore keeps the ordinary public/ output and creates no fake provider file just to make the preset look busier.
What Nift creates
--target=supabase intentionally starts from the same static HTML project shape as ordinary nift init:
content/
templates/
public/ # Nift build output
.nift/
The target gives the CLI a consistent platform vocabulary and gives the documentation a clear integration entry point. It does not pretend Supabase consumes a special Nift deployment artifact.
Add Supabase when you need it
Supabase's own CLI uses supabase init to create a supabase/ directory containing config.toml. Run that separately when the project actually needs local Supabase development rather than making every Nift starter carry unused backend configuration.
supabase init
supabase startDynamic functionality
A Nift frontend can use Supabase's browser-facing APIs for database-backed features, authentication, storage and realtime data. For server-side work, Supabase Edge Functions use the Supabase Edge Runtime and are deployed separately with the Supabase CLI.
Nift static frontend ─────► static host
│
└───────────────► Supabase
├─ Postgres
├─ Auth
├─ Storage
├─ Realtime
└─ Edge Functions
Hosting boundary
Deploy Nift's generated public/ frontend with a static host and connect it to Supabase as the backend. Supabase Edge Functions can expose HTTP endpoints, but they are not the ordinary static-site hosting model represented by Nift's deployment-oriented targets.