What is Dreamlit?
What is Dreamlit?
Dreamlit is an AI-powered email automation platform that lets you create beautiful, production-ready notification workflows by simply chatting with AI.Unlike traditional notification services that require API integration and manual template building, Dreamlit connects directly to your database and uses specialized AI to generate complete workflows—including templates, copy, and logic—from plain English descriptions. This database-driven approach means notifications work independently from your app code, allowing each system to excel at what it does best.
Who is Dreamlit for?
Who is Dreamlit for?
Dreamlit is perfect for:
- Vibe coders using Lovable, Bolt, Cursor, or Replit who want professional notifications without the complexity
- Founders and solopreneurs who need to ship fast without getting bogged down in email infrastructure
- Small teams who want marketing-quality emails without hiring specialists
- Anyone using Supabase who needs production-ready auth emails (Supabase’s defaults aren’t meant for production)
What types of notifications can Dreamlit handle?
What types of notifications can Dreamlit handle?
Dreamlit handles all types of email notifications your app needs:
- Auth emails: Password resets, magic links, email verification (especially for Supabase Auth users)
- Transactional: Order confirmations, payment receipts, account updates
- Scheduled: Weekly digests, trial expiring reminders, subscription renewals
- Onboarding sequences: Welcome series, feature tutorials, win-back campaigns
- One-off campaigns: Product launches, announcements, surveys
- Internal alerts: New signups, failed payments, form submissions (via email or Slack)
How is Dreamlit's AI different from general coding assistants?
How is Dreamlit's AI different from general coding assistants?
While tools like Cursor, Lovable, or Bolt are great general purpose coding assistants, Dreamlit’s AI is laser-focused on notifications:
- Specialized training: Our AI is fine-tuned specifically for notification workflows
- Context-aware: Understands your database schema to make intelligent suggestions
- Proactive clarification: Asks questions when schemas are ambiguous rather than guessing
How does Dreamlit work?
How does Dreamlit work?
Dreamlit uses your database as the source of truth to trigger notifications:
- Easy Setup: Our guided flow walks you through connecting your database and configuring your email sender
- Instant Workflow Creation: Simply describe what you want in plain English, and our Workflow Agent generates the complete workflow—trigger logic, templates, and copy
- Database Events: Your app continues to write to your database normally (user signups, payments, etc.)
- Automatic Execution: Dreamlit monitors these database changes and executes the appropriate workflows, handling all scheduling, retries, and delivery
Why does Dreamlit use the database instead of APIs?
Why does Dreamlit use the database instead of APIs?
Your database is already the source of truth for your application. Using it as the integration point provides several key advantages:
- Zero coupling: Your app doesn’t need to know about Dreamlit—it just saves data normally
- Self-documenting: Database schemas provide context that AI can understand immediately
- Natural events: Data changes ARE the events—no need to explicitly trigger notifications
- Separation of concerns: Let your app’s AI focus on UX while Dreamlit’s AI specializes in notifications
- No lost events: Even during downtime, database triggers ensure events are captured
How does Dreamlit work with Supabase Auth?
How does Dreamlit work with Supabase Auth?
If you’re using Supabase Auth, Dreamlit can handle all your auth emails (password reset, magic links, email verification, etc.) with custom templates instead of Supabase’s basic defaults.Important differences from regular workflows:
- Auth emails trigger from Supabase API calls (
supabase.auth.signUp(), etc.), NOT database changes - Our setup process automatically configures the necessary Auth Hook for you
- Your app must call the appropriate Supabase auth methods to trigger emails
supabase.auth.resetPasswordForEmail(). The auth hook intercepts this and Dreamlit sends your beautifully designed password reset email.This is crucial because Supabase’s default email service isn’t meant for production. With Dreamlit, you get production-ready auth emails without touching SMTP settings or writing auth hooks yourself.Learn more about Supabase Auth configuration →Will Dreamlit affect other database operations?
Will Dreamlit affect other database operations?
Any Dreamlit installed triggers will be run AFTER the relevant database operation in a non-blocking fashion.Dreamlit’s triggers are simple and lightweight (only an INSERT operation in the
dreamlit schema) and are very unlikely to fail. But even if the trigger fails
for whatever reason, the underlying database operation will still succeed. We have an explicit try catch block in the
trigger procedure to ensure this.Is there performance overhead with Dreamlit's database triggers?
Is there performance overhead with Dreamlit's database triggers?
Database triggers in general are highly performant with minimal overhead.Furthermore, Dreamlit’s triggers only perform an INSERT operation (into a separate
dreamlit schema) to log the event and nothing else (no querying, etc). The events are picked up
in a separate polling loop.This “insert into a separate table” database trigger pattern is a common pattern in database design and have been battle tested for decades.Is it possible for notification events to get dropped or lost?
Is it possible for notification events to get dropped or lost?
No. Dreamlit is designed for reliability.Even if your database is temporarily unavailable or Dreamlit experiences an outage, events will continue to be logged in the Dreamlit-managed
schema. When systems come back online, all unprocessed events will be picked up and executed in order.
How does Dreamlit handle failures?
How does Dreamlit handle failures?
To ensure robustness around transient errors (for instance, if your database is unavailable due to network connectivity issues), Dreamlit
automatically retries failed workflow steps with exponential backoff.If a workflow fails after exhausting all retries, it will be marked as failed and you will be notified.You can also configure custom error handling for specific workflows.
What happens if my database goes down?
What happens if my database goes down?
If your database is fully unresponsive, alongside the rest of your application, your workflows will pause until connectivity is restored.When your database comes back online, Dreamlit will process all accumulated events in the correct order. No notifications will be lost
during the downtime.
What if the event I want to trigger on isn't in my database?
What if the event I want to trigger on isn't in my database?
Most application events are already reflected in your database—user signups, payments, status changes, etc. These are likely already being persisted naturally as part of your app’s operation.If you find an event that isn’t captured, simply add it to your data model. This is actually a best practice—your database should be the source of truth for all application state.For Supabase Auth users, auth events work differently through API hooks. Learn more →
How do I ensure my notifications don't break when I change my database schema?
How do I ensure my notifications don't break when I change my database schema?
There are several strategies to ensure that your Dreamlit workflows stay intact as you make changes to your database schema.You can read more here.
How do I know that my data is secure?
How do I know that my data is secure?
At Dreamlit, we take security seriously. Dreamlit implements multiple layers of security to protect your data:
- All database connections use encrypted TLS
- Database access is limited to only the tables and operations needed
- All sensitive data is encrypted both in transit and at rest
- Regular security audits and penetration testing