“Using Neon with Neon Auth just made everything simpler. Our database and auth live in the same place, and it’s the kind of backend you forget it exists. That’s exactly how it should be”
Gabriel Tumlos, Founder of Daisy
Daisy is a generative media studio building tools that make creativity instant. Their main app lets anyone generate and remix images or videos, with a growing collection of smaller “mini apps” that focus on specific formats and ideas. Each mini app is self-contained, simple to use, and designed to capture a moment in its best light. Simply upload a headshot, a product, or an idea for an outfit, a poster, or a meal, and Daisy takes it from there.
That rhythm of constant release defines Daisy’s philosophy. The team builds for what they call “the generation that refuses to wait” – creators who expect expressive tools to work as fast as they think.
Picking a Backend That Just Works
For Daisy, the backend has to be as seamless as their creative process. Every new app they launch needs access to the same user accounts, generations, and referral data without extra setup or configuration. The team’s stack reflects that balance of automation and simplicity – Ingest manages job queues, Railway handles deployments, and Neon powers the database and authentication.
When they first came across Neon, they adopted it almost immediately. Setup was fast, automation was easy, and the experience matched the team’s preference for tools that get out of the way. Once integrated, Neon became part of Daisy’s weekly release rhythm. New mini apps can plug into the same shared database and auth layer with minimal work.
“It was pretty quick to get started, and once we automated the setup, Neon just became part of how we ship” (Gabriel Tumlos, Founder of Daisy)
Unified Login with Neon Auth
Authentication was one of the trickiest parts of Daisy’s early setup. Each new app needed to manage user signups, sessions, and permissions, but rebuilding that flow for every release would become unmanageable. So Daisy wanted a single authentication system that could cover every app in their ecosystem without extra services or synchronization.
That’s where Neon Auth comes in. It lets Neon developers manage users and sessions within the same database that stores their application data, avoiding them to setup a separate auth database or API proxy and simplifying their setup.
“Neon Auth was already part of our database, so it just made sense. It speeds things up and keeps everything in one place” (Gabriel Tumlos, Founder of Daisy)
For Daisy, this structure solved three problems at once:
- Unified flow: Every Daisy app uses the same Google login through Neon Auth, ensuring users only sign in once across the entire platform.
- Simplified onboarding: Auth data lives in the same database as generations and referrals, so no schema duplication or sync logic is needed.
- Faster rollout: Adding a new mini app is as simple as approving it inside Neon Auth’s configuration list. Once added, it inherits the same secure OAuth flow automatically.
Here’s what that looks like in practice for them:
- Daisy maintains a single Neon project where both app data and user identities live.
- When a new mini app launches, it’s registered with Neon Auth by adding its domain or client ID to the approved apps list.
- The app then automatically connects to the shared login system, reusing the same Postgres-backed sessions and user table.
Wrap Up
Daisy’s setup is simple and effective – one database, one auth layer, and a smooth backend that allows them to keep their rhythm of steady releases. Try a similar setup for your own app with the Neon Free Plan, and don’t forget to explore Neon Auth.
A big thank-you to Daisy for sharing their stack with us. Explore their platform: https://app.daisy.so/
