About Mailoo
Customer-facing content and conversations without the integration fiction
Our mission
Teams should not need a dozen tools—or OAuth access to personal inboxes—just to run a blog, capture leads, send campaigns, and chat with visitors. Mailoo is built around integrations you actually ship: FORM and CONTACT_FORM endpoints, the JSBOX widget, and the headless blog API.
Everything runs behind versioned REST APIs, scoped API keys, and the dashboard you already use for projects. When you need to send mail to subscribers, you bring your own SMTP settings on the integration—Mailoo stays the control plane, not another mailbox client.
Headless blog
Editorial workflow in the dashboard, delivery over HTTPS APIs.
Subscribers & campaigns
List growth tied to form integrations and template-based sends.
Website forms
Server-side webhooks and API keys—no exposed secrets in the browser.
JSBOX chat
Embeddable realtime widget with dashboard and websocket tooling.
Our values
Simplicity
We document the paths that exist today—projects, integrations, messages—so you can go live without guessing which connector is "coming soon".
Reliability
Communications infrastructure should be observable, rate-limited where it matters, and honest when a dependency (like SMTP) is missing.
Innovation
We iterate on the API surface, dashboard workflows, and developer ergonomics based on how teams actually run their sites.
Ready to get started?
Spin up a project, add the integrations you need, and wire them from your backend.