One project. Email, social, and forms.
Today you run product messages across email, social, and forms in the same OnePush project. REST for apps, MCP for agents. Next: one Message model, one composer, one approval inbox.
Stop stitching three vendors
Contacts, campaigns, social posts, and lead forms share one identity. Humans review in the dashboard; agents draft over MCP with confirm before publish.
- ✓Transactional email and campaigns
- ✓Social draft, schedule, and publish
- ✓Forms into the same contact graph
Email your users, post on LinkedIn and X, capture waitlist leads without switching tools.
Built for product teams, not creator agencies
We compete on shared contacts and agent access, not on racing 30 social networks.
Email first
Transactional send and automations are the trust layer every SaaS already needs.
MCP for agents
Revocable mcp_ keys. Draft and schedule social; publish only with confirm.
Social in-project
X, LinkedIn, Instagram, Facebook, Pinterest. Same dashboard as email.
Honest roadmap
Shared Message model and calendar next. Then Slack/Discord. Then SMS/WhatsApp if ICP asks.
Ship a product update across surfaces
Coordinate in one project now. Unify the composer as we ship Phase A.
Verify domain
Attach SPF / DKIM so transactional and campaign email can leave.
Connect social
OAuth the networks you need for the launch.
Send and schedule
Run an email campaign and schedule social from the dashboard or MCP.
Capture and follow up
Forms feed contacts; automations continue the conversation.
Start with the project you already need
Email + social + forms today. Shared composer and Slack/Discord after the medium is real. See docs/POSITIONING.md.