Designed from your codebase
Every email looks like your product. Because it starts from your code.
Connect your GitHub repo and Signature's agent reads the design system you actually
ship — your tailwind.config, theme tokens, and components. The palette, the
type scale, the button radius. Your design system is the brand kit.
- Reads tokens straight from the repo — no brand-kit form to fill in
- Colors, typography, spacing, and radii mapped to email-safe styles
- Not a template gallery — designs generated from what your app really looks like
export default {
theme: {
extend: {
colors: {
brand: {
500: '#6366f1',
600: '#4f46e5',
},
ink: '#0f172a',
},
fontFamily: {
sans: ['Inter', 'system-ui'],
},
borderRadius: { xl: '14px' },
},
},
}Design tokens · acme/web
One conversation → a whole journey
Describe the lifecycle. Get the graph.
Tell the agent “onboard new users, branch on paid tier, re-engage after 7 days quiet” and it builds the full visual journey — triggers, delays, branches, sends — grounded in your real database columns and PostHog events, not hypothetical fields.
Then edit everything by hand: journeys are node graphs on a canvas with live audience estimates, and emails are block documents compiled through MJML with cross-inbox previews — Outlook, Gmail, Yahoo, and Apple Mail approximations before anything sends.
Coming · early access
Your emails ship with your code.
A rebrand lands. A feature gets renamed. Pricing changes. Today, your lifecycle emails quietly drift out of date. Soon, when your repo changes, Signature proposes design and copy diffs to match — you review the before/after and approve.
The same agent that read your design system watches it evolve. Launching soon for early-access teams.
a1f9c3e rebrand: swap primary from blue to brand indigoHow it works
Three steps to lifecycle email that keeps up.
Connect repo + data
Install the GitHub App on your repo. Point Signature at your Supabase (read-only) and PostHog. The agent maps your design system and your real audience.
Describe the journey
One conversation: who it's for, what triggers it, how it branches. The agent drafts the graph and every email in it — in your product's own design language.
Approve and send
Review on the canvas, preview across inboxes, then ship. Every send goes out through your own AWS SES — your domain, your reputation, your quotas.
Your infrastructure, your data
Signature reads. It doesn't hoard.
Your Supabase, read-only
Audiences come from the database you already have. Signature queries your columns — it never copies your customer table into another vendor's warehouse.
Your PostHog events
Triggers and behavior branches run on the product events you already track. “7 days quiet” means your definition of quiet.
Your AWS SES
Every email sends through your own SES account — your sending domain, your deliverability reputation, your quotas. Signature never proxies your mail.
Your data never lives anywhere new. Signature is a control plane over infrastructure you already own — read-only where it can be, and explicit everywhere it acts.
Email that keeps up with your product.
We're onboarding a small number of software teams by invitation. If your lifecycle email should look like your product — talk to us.
Early access. By invitation. · hello@usesignature.ai