01
One view per client
A dashboard listing that client’s projects and their status, a project page with updates in date order, a file area, and an approval button where you need a yes before you continue.
Use case — web app
Build a client portal your clients will actually log in to
Client work leaks across tools. The latest file is in one email, the approval is in another, and the status lives in your head until the client asks for it. A client portal fixes that with four things: a login per client, the projects that belong to them, the files and updates for each one, and a clear place to approve. Vibely builds all four from a description, on a Postgres database with authentication via Supabase, and deploys it to a URL you can send to your first client the same day.
- Postgres, auth and file storage on your own Supabase project
- Row-level rules so each client sees only their own work
- Deploys to a live URL — nothing for your team to install
- React and TypeScript you own, synced to GitHub on Pro and Business
- Add a stage, a field or a new view by asking
- Free plan, no credit card, unlimited projects
Start with this prompt
Paste it in and edit the details to match your own. Being specific about the screens and the data is what separates a working app from a mockup.
Build a client portal for a small design studio. Screens: a sign-in page; a client dashboard listing their projects with a status badge (In progress, Waiting on you, Done); a project page with a timeline of updates, a file list with upload and download, and an Approve button for the current deliverable; and an admin area where the studio sees every client and project. Data: clients, projects, updates, files and approvals in Supabase, with files in Supabase Storage. Each client only sees their own projects. Studio staff see everything. Add two example clients with a few projects each so I can see it working.
What to build next
- Email the client when a project moves to Waiting on you.
- Add a comments thread under each update.
- Add an archive view for finished projects.
Web app
What the build actually consists of
This is for consultants, agencies, accountants, designers and studios with somewhere between a handful and a few hundred clients, who are tired of explaining where the latest version is. If you need contracts, e-signatures and invoicing in one suite, a dedicated product will cover more ground — the case here is a portal that matches how you deliver, under your own brand.
02
Access that is actually scoped
Postgres and authentication on Supabase, with row-level rules so each client only ever sees their own projects and files, while your team sees everything. Files live in your own Supabase project.
03
Your brand, your URL
Your colours, your logo and your wording, deployed to a live URL on the first build. Connect a custom domain on Pro and Business so clients see your name, not ours.
What you get
- A sign-in for each client, scoped to their own projects
- Project pages with status, updates and a file area
- An approval step with a record of who approved what, and when
- An admin view for your team across every client
- A live URL, plus a GitHub repository you control on Pro and Business
Describe it. Watch it build.
Paste the prompt above and react to something running instead of writing a spec. The free plan needs no card, and the code is yours from the first build.
Start buildingFAQ
Questions, answered.
Can each client only see their own files?+
Yes. Ask for row-level security scoped to the client, and the rules are written into your Supabase database, not just hidden in the interface. They are in your code, so you can read them and tighten them.
Can I use my own domain?+
Every build deploys to a live URL straight away. Custom domains are on the Pro and Business plans, so clients can sign in at an address with your name on it.
Can it send emails to clients?+
Not as a built-in connector. Vibely ships nine connectors — Vibely AI, Supabase, Stripe, RevenueCat, GitHub, Notion, Linear, Figma and Miro. Sending email is an API call to a provider you choose, written in your own code, which the agent can add when you ask.
Can clients pay invoices in the portal?+
You can add payments with the Stripe connector — for example a pay-now button on an invoice. Describe how you bill and the agent wires the checkout into the portal.