fromHello

<div align="center">

<a href="https://fromhello.io/?utm_source=github&utm_medium=readme"><img src="assets/hero.webp" width="100%" alt="fromHello. Open-source marketing automation. You didn’t start this to stay small. fromHello tracks what people do on your site and in your app, segments them in real time and runs journeys across email, SMS, in-app and ad audiences."></a>

<br/> <br/>

<a href="https://fromhello.io/?utm_source=github&utm_medium=readme#waitlist"><picture><source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/Synapsr/fromHello/main/assets/btn-waitlist-dark.svg"><img src="https://raw.githubusercontent.com/Synapsr/fromHello/main/assets/btn-waitlist.svg" height="48" alt="Join the waitlist"></picture></a>      <a href="https://github.com/Synapsr/fromHello"><picture><source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/Synapsr/fromHello/main/assets/star-link-dark.svg"><img src="https://raw.githubusercontent.com/Synapsr/fromHello/main/assets/star-link.svg" height="48" alt="Star this repo"></picture></a>

<br/> <br/>

<a href="LICENSE"><picture><source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/Synapsr/fromHello/main/assets/badge-license-dark.svg"><img src="https://raw.githubusercontent.com/Synapsr/fromHello/main/assets/badge-license.svg" height="28" alt="License: AGPL-3.0"></picture></a> <a href="#your-ai-plugged-in"><picture><source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/Synapsr/fromHello/main/assets/badge-mcp-dark.svg"><img src="https://raw.githubusercontent.com/Synapsr/fromHello/main/assets/badge-mcp.svg" height="28" alt="MCP: 59 tools"></picture></a> <a href="https://fromhello.io/?utm_source=github&utm_medium=readme#waitlist"><picture><source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/Synapsr/fromHello/main/assets/badge-waitlist-dark.svg"><img src="https://raw.githubusercontent.com/Synapsr/fromHello/main/assets/badge-waitlist.svg" height="28" alt="Waitlist open"></picture></a>

<br/> <br/>

<a href="#then-act-on-what-each-person-does">Product</a>  ·  <a href="#your-ai-plugged-in">AI and MCP</a>  ·  <a href="#how-it-all-comes-together">Use cases</a>  ·  <a href="#hosted-by-us-or-on-your-servers">Hosting</a>  ·  <a href="#good-to-know">FAQ</a>

</div> <br/>

[!NOTE] This is fromHello’s public repository. The platform source isn’t published here yet. Join the waitlist for early access to fromHello Cloud, and star the repo to help more teams find it.

What is fromHello

fromHello is open-source marketing automation: first-party tracking, real-time segments and journeys triggered by what people do on your site and in your product, with email, SMS, in-app, web push and ad audiences in one platform. Use it on fromHello Cloud, or self-host it under AGPL-3.0.

From anonymous visitor to paying customer.

fromHello covers every step in between.

<img src="assets/cards.svg" width="100%" alt="One person’s timeline, from anonymous visitor (anon_7f3c2a) to trial user (alex@acme.com) to paying customer, beside four cards: Spot who’s ready to buy (the High intent segment), Visitors who left come back (web push and an ad audience), Trials don’t go quiet (email, in-app, SMS), See what converts (a visitor, trial, paid funnel). Example data.">

• Every visit counts, even before signup. Site and app events land on one profile. At signup, the anonymous history joins the contact.
• Spot who’s ready to buy. Real-time segments update on every event.
• Visitors who left come back. Web push and ad audiences, before signup.
• Trials don’t go quiet. Journeys start on events: email, in-app, SMS.
• See what converts. Goals and funnels, from first visit to paid.

Connect everything in one place.

What you know about each person, all in one profile.

<img src="assets/hub.svg" width="100%" alt="Ten kinds of business data flow into fromHello and one profile: website (visits, clicks, forms), product usage (events from your app), ad campaigns (UTMs, click IDs), SMS (replies, opt-outs), email (opens, clicks, replies), payments (trials, plans, revenue), CRM (company, custom fields), feedback (NPS, survey scores), spreadsheets (contacts and events) and preferences (consent, unsubscribes). The example profile: Alex Moreau, head of operations at Acme, a paying customer, first touch paid search, last visit the pricing page, plan Pro annual, last reply 2 days ago, NPS 9, anonymous history merged at signup. Data comes in through the tracking snippet, the API, a CSV import or the email and SMS providers you connect.">

Then act on what each person does.

Segment them, run journeys, read replies, track goals.

<img src="assets/tour.svg" width="100%" alt="Four areas of the platform. Journeys: journeys that wait for people, not dates. Segments: who opened, who clicked, who never replied. Channels and inbox: the message goes out, the reply shows up on their profile. Results: judge each journey by its goals."> <details> <summary><b>Journeys.</b> Journeys that wait for people, not dates.</summary>

• Wait for event: one path when it happens, another on timeout.
• Branch on a profile field, an event or a segment. First match wins.
• 14 node types, including A/B split, webhook and goal.

</details> <details> <summary><b>Segments.</b> Who opened, who clicked, who never replied.</summary>

• Filter by event, profile field, message status or suppression.
• Event rules: at least N times, over all time or a rolling window.
• Nest AND/OR groups and watch the match count as you edit.

</details> <details> <summary><b>Channels & inbox.</b> The message goes out. The reply shows up on their profile.</summary>

• Email through Resend, Postmark, SendGrid, SMTP or Microsoft 365.
• SMS, in-app banners and modals, opt-in web push and ad audiences.
• A reply can start a journey, or wake one that’s waiting for it.

</details> <details> <summary><b>Results.</b> Judge each journey by its goals.</summary>

• Entered, completed and failed per journey, over 7, 14, 30 or 90 days.
• A goal funnel: how many reached each one.
• A/B splits call a winner only with enough data and a significant lift.

</details>

Your AI, plugged in.

Use the AI subscription you already have to ideate, build, track, analyze and improve. 59 tools, one MCP server.

<img src="assets/ai.svg" width="100%" alt="An example session in Claude Code asks: draft a welcome journey for new signups, show me before publishing. Through fromHello’s MCP server it calls create_template, create_journey_draft, then publish_journey, which waits for your approval. Beside it, the dial of all 59 MCP tools, grouped as playbooks, segments, journeys, templates, tracking, analytics, people and approval. The loop: ideate, build, track, analyze, improve.">

Works with Claude, Claude Code, Cursor, Codex or any MCP client. No AI tool in fromHello sends a message, and a journey your agents build stays a draft until it’s published. MCP calls are never metered. No AI subscription? From Team up, cloud plans include AI credits for the built-in assistant.

How it all comes together.

Six plays to grow your business.

<img src="assets/plays.svg" width="100%" alt="Six plays. Paid acquisition: turn high-intent visitors into named leads. Sales: hand sales the trials that invited their team. Expansion: offer the upgrade when they hit the limit. Payments: recover failed payments before they cost a customer. Retention: turn cancellations into conversations. Reviews: ask your promoters for a review while they’re still glowing.">

Hosted by us, or on your servers.

Two ways to run fromHello.

<img src="assets/hosting.svg" width="100%" alt="fromHello Cloud, recommended: nothing to install, nothing to upgrade. Self-host, AGPL-3.0: run it yourself, with or without us. Data and control, either way: export and erase, automatic suppression, audit log, workspaces and roles, your sending domain, first-party tracking.">

• fromHello Cloud. We run Postgres, Redis and every upgrade. From Team up, email sending is set up for you and AI credits are included. Join the waitlist
• Self-host. The source isn’t published here yet. Self-hosted, fromHello runs on your own servers: Postgres 18+, Redis 8+, an API, a worker, the dashboard and an optional MCP server. You run upgrades and backups, with your own sending provider and AI key, or local models through Ollama.

<details> <summary><b>Data and control, either way</b></summary>

• Export and erase. Export a contact as JSON, or erase their profile and messages, through the API. Every erasure is audit-logged.
• Automatic suppression. Unsubscribes and bounces feed a suppression list, checked before every send.
• Audit log. Invites, API keys, sending settings, consent changes, erasures and MCP tool calls.
• Workspaces and roles. Separate workspaces, four roles from owner to viewer, and API keys scoped to one workspace.
• Your sending domain. Email goes out from your own domain, so its reputation is yours.
• First-party tracking. Our tracking loads no third-party pixels.

</details>

Good to know.

The code, self-hosting, following along, the AI, your data, the stack and the price.

<details> <summary><b>Where’s the source code?</b></summary> <br/>

The platform source isn’t published here yet. This repository holds the README, the AGPL-3.0 license, project files and images: there’s no code here to clone, build or run, and no codebase to report bugs against or send pull requests to. A contribution guide covering setup, architecture and conventions will land with the source. To report a security issue, follow SECURITY.md, never a public issue.

</details> <details> <summary><b>Can I self-host fromHello today?</b></summary> <br/>

No. The source isn’t published here yet, and self-hosting needs it. Self-hosting is part of fromHello, under AGPL-3.0, and a self-hosting guide will land with the source. Beyond what the hosting section lists, a self-hosted install needs two domains with TLS: one for the dashboard and one for the API. The API must be reachable from the internet for provider webhooks, the tracking snippet and unsubscribe links.

</details> <details> <summary><b>How do I follow along?</b></summary> <br/>

A star saves this repository to your Stars list and helps more teams find fromHello, but GitHub sends no notifications for it. For early access to fromHello Cloud, join the waitlist: it opens in stages, and we email you when your spot opens.

</details> <details> <summary><b>What can AI change without my approval?</b></summary> <br/>

No AI tool in fromHello sends a message, but AI actions can change live journeys without a confirmation step. Publishing, pausing or deleting through an agent takes a second, confirming tool call, which your AI client can ask you to approve. Other edits, such as changes to a segment, a template or a live journey’s exit condition, apply when saved. Opt-in send-time personalization rewrites each email without per-message review. If the AI fails, the send waits by default.

</details> <details> <summary><b>Does fromHello work without AI?</b></summary> <br/>

Yes. Tracking, segments, journeys and sending work with no AI set up. To add AI, connect the AI client you already use over MCP: it brings its own model, so fromHello needs no AI key for it. Self-hosted, fromHello’s own AI features take your key for Anthropic, OpenAI or Google, or run on local models through Ollama.

</details> <details> <summary><b>Where is my data stored?</b></summary> <br/>

On fromHello Clou