Skip to content
Start building

A real backend

Connect your Supabase account and pick a project. The agent designs the tables, writes migrations and row-level security, and adds sign-in and storage.

Start building

Vibely builds your app’s backend in your own Supabase project: Postgres, sign-in, file storage, realtime and Edge Functions. Connect your Supabase account, pick a project, and the agent writes the migrations and row-level security policies for you. Stripe handles payments on the web and RevenueCat handles in-app purchases on mobile.

The parts every real app needs

Ask for a feature that needs saved data or accounts, and Vibely sets up the backend for it.

  • Postgres tables and migrations

    Tables, relationships and views, created by SQL migrations you can read in the project.

  • Row-level security by default

    Every table the agent creates gets RLS and policies in the same migration, so one user’s rows aren’t served to another.

  • Sign-in

    Email and password, magic links, and Google, Apple or Microsoft sign-in through Supabase Auth, including Sign in with Apple on iOS.

  • File storage

    Uploads such as avatars, photos and documents, stored in your Supabase project with access rules.

  • Realtime and Edge Functions

    Live updates when rows change, plus server-side code for webhooks, scheduled jobs and calls that need a secret key.

  • Encrypted secrets

    Vibely asks for API keys in the editor and stores them encrypted, never in the chat or your code.

How it works with your data

  • Ask, and the schema follows

    “Let signed-in people save their favourite drinks” becomes a migration with the table, row-level security and the policies, applied to your project.

    supabase/migrations/0001_favourites.sql
    create table public.favourites (
  id uuid primary key default gen_random_uuid(),
  user_id uuid not null references auth.users on delete cascade,
  item_id text not null,
  created_at timestamptz not null default now()
);
alter table public.favourites enable row level security;
create policy "Read own favourites" on public.favourites
  for select using (auth.uid() = user_id);
create policy "Add own favourites" on public.favourites
  for insert with check (auth.uid() = user_id);
    • Applied migration 0001_favourites.sql
    • Row-level security enabled on public.favourites
    • 2 policies created

  • Keys go in a secret, not the chat

    When Stripe or another service needs a key, Vibely opens a secret prompt. Paste the value there and it’s saved encrypted to the project.

    Add a secret

    Vibely needs your Stripe secret key to take payments. Paste it here, not in the chat: it is saved encrypted to this project.

    Name
    STRIPE_SECRET_KEY
    Value
    sk_test_••••••••••••••••••Show value

    Server-only values are never written into your code; they are sent to your connected Supabase project’s Edge Function secrets when you save.

    CancelSave secret

  • Data protected by policies, not screens

    Access rules live in the database, so hiding a button is never the only thing between a visitor and someone else’s data. After each migration Vibely checks for tables left open.
    Scan your app for security issues

  • It’s your Supabase: you own the data

    The project lives in your Supabase organization. Vibely connects on your behalf to run migrations and deploy functions; the data stays in your account.
    Set up the Supabase connector

Charge for it

Payments use the same backend: subscriptions and checkout on the web, in-app purchases on mobile.

  • Stripe on the web

    Give Vibely your Stripe key (a test key while you build) and ask for checkout or a subscription. The app checks each customer’s status, so you don’t need a webhook to launch.

    Add Stripe Checkout, step by step

  • RevenueCat on mobile

    For iOS and Android apps, RevenueCat handles in-app purchases and subscriptions from the App Store and Google Play, with a paywall the agent builds.

    Set up the RevenueCat connector

The connectors behind it

More resources

Frequently asked questions

Yours. The backend is a normal Supabase project in your own Supabase organization, on your own Supabase plan, and Supabase bills you directly. Open it in the Supabase dashboard, query it, back it up, or keep using it if you leave Vibely.

No. Create the project at supabase.com, then connect your Supabase account in Vibely and pick it. Until you do, the agent keeps building on mock data so you can see the feature first.

Every table the agent creates gets row-level security and policies in the same migration, and Vibely checks afterwards for tables with it turned off. You can also run the security scan for a full check.

Into a secret, not the chat. When a feature needs a key, Vibely asks for it in the editor. Server-only values go to your Supabase project’s Edge Function secrets and are never written into your code.