How does the 24-hour delivery actually work?

Once you submit your project request and we approve it, our team starts building immediately. We work in focused sprints, handling everything from frontend to backend to deployment. You receive regular updates throughout the process.

What tech stack do you use?

We build with Next.js 14+ (App Router), TypeScript, Tailwind CSS, NextAuth for authentication, PostgreSQL for database, and Stripe for payments. This stack is proven, scalable, and easy to maintain.

Upon full payment, you receive ownership of the source code, GitHub repository, database schemas, and configuration files created for your project. See our Terms of Service for details on deliverables and third-party components.

What if I need changes after delivery?

All plans include a support period (7–30 days depending on tier) where we help with bug fixes and minor adjustments. For larger changes, we offer additional development at competitive rates.

Can you handle custom integrations?

Yes. Our Custom tier includes integrations with third-party APIs, services, and platforms. Tell us what you need during the project request phase.

We set up everything on your own infrastructure — whether that is Vercel, Railway, or a VPS. You own the hosting account and have full control. We provide the initial setup and deployment.

What happens if my idea is too complex?

We review every request before starting. If your project requires more time, we suggest a custom timeline or break it into manageable phases. We are transparent about what is achievable in 24 hours.

Do you offer refunds?

If we cannot deliver the scope in your approved tier or custom quote within the agreed timeline, we will refund fees paid for that project. Other refund requests are handled as described in our Terms of Service.

PostgreSQL vs Supabase for Founder MVPs

TL;DR: Both are PostgreSQL under the hood. Supabase is faster to bootstrap (auth, storage, dashboard). Plain Postgres + NextAuth gives you more control and simpler mental model for fixed-scope MVPs. We default to PostgreSQL + NextAuth on every ShipInADay build.

Founders ask whether they need Supabase on day one. The honest answer: you need a relational database and a clear ownership model — the brand on the box matters less than scope.

What Supabase adds

Hosted Postgres with a nice dashboard
Built-in auth, storage, and realtime subscriptions
Client SDKs that feel like Firebase for SQL
Fast prototypes when your team already knows the stack

What plain PostgreSQL adds

No vendor-specific SDK lock-in on day one
Standard SQL migrations you can run anywhere (OVH, RDS, Neon, etc.)
Pairs cleanly with NextAuth for session + OAuth in Next.js
Easier to reason about in a 24-hour fixed scope

Comparison for MVP stage

Need	Supabase	Postgres + NextAuth
User accounts	Built-in	NextAuth + `users` table
Row-level security	Native policies	App-layer checks (our default)
File uploads	Storage bucket	S3/R2 when needed
Realtime	Built-in	Defer unless core to v1
Portability	Good SQL export	Excellent — it's just Postgres

Our default (and why)

Every Launch and Scale tier ships with:

PostgreSQL 16
NextAuth (Google + credentials)
Migrations in-repo (database/migrations/)
user_id ownership on project data — no email-only access

That stack answers 90% of founder MVPs without adding a BaaS dependency on day one.

When we recommend Supabase instead

You already have Supabase in production and need a fast extension
Realtime collaboration is the product (not a nice-to-have)
Your team has zero backend capacity and wants the dashboard on day one

Custom tier projects can integrate Supabase when it is explicitly in scope.

FAQ

Can I migrate from Supabase later?
Yes — it's PostgreSQL. Plan for auth migration (sessions, user IDs) as the hard part, not the data.

Do you host the database?
We deploy your MVP with a defined hosting path; production DB strategy is documented at handoff.

Next step

Pick a tier, read what to prepare, and start your request.