Skip to content
fromHello
Open-source marketing automation

You didn’t start this to stay small.

fromHello tracks what your visitors and customers do, segments them in real time and runs journeys across email, SMS, in-app and ad audiences.

Join the waitlistStar on GitHub

From anonymous visitor to paying customer. fromHello covers every step in between.

Example data

Every visit counts, even before signup.

  1. Anonymous visitoranon_7f3c2aViewed pricing twiceDay 1
  2. Trial useralex@acme.comStarted a trialDay 4
  3. Paying customerChose a paid planDay 18

Site and app events land on one profile. At signup, the anonymous history joins the contact.

Anonymous visitor: Spot who’s ready to buy.

High intent

Recomputed on every event, before signup too.

  • Segment: High intent, no signup. Viewed pricing 2+ times in 7 days, no trial.
  • anon_7f3c2a entered the segment.

Anonymous visitor: Visitors who left come back.

Web pushAd audience

Both reach visitors before signup, with their consent.

  • Web push from yourapp.example: Still comparing plans?
  • Ad audience: Pricing visitors, fed by your ad pixel.
  • anon_7f3c2a is back on pricing.

Trial user: Trials don’t go quiet.

  1. Email
  2. In-app
  3. SMS

Started by an event, then email, in-app and SMS.

  • Live journey: Trial onboarding.
  • Trigger: trial started. Email: replied. In-app: clicked. SMS: delivered.

Paying customer: See what converts.

  • Visitor
  • Trial
  • Paid

Goals record the conversion, from first visit to paid.

  • Alex Moreau: goal reached, paid plan.
  • Funnel: visitor, trial, paid.

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

Example data

Data sources, all flowing into fromHello

  • 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
  • Preferences: Consent, unsubscribes

Example profile in fromHello

  • Alex Moreau, Head of operations at Acme, alex@acme.com.
  • Segment: Paying customer, from payments.
  • First touch: Paid search, from ad campaigns.
  • Last visit: Pricing page, from the website.
  • Plan: Pro, annual, from payments.
  • Last reply: 2 days ago, from email.
  • NPS: 9, from feedback.
  • 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.

Journeys

Journeys that wait for people, not dates.

Journeys that wait for people, not dates.

  • 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.

Example journey Welcome series, open in the journey builder, active and live as version 3. Entry on signed_up leads to a branch with two named branches, where the first match wins: Viewed pricing (pricing_viewed at least 2 times in the last 7 days) and Everyone else (email is set). Each branch sends its own email, then both reach an A/B split named Welcome email, set to 50/50, which routes each person to one of two emails. A Wait for event node then waits up to 3 days for feature_used. On the event, the journey reaches the goal Activated. On timeout, it exits. The settings panel of the wait is open. On wide screens, a palette lists all 14 node types in four groups: triggers, actions, flow control and endings. The header holds Save draft and Publish v4. On narrower screens the canvas starts lower in the journey, at the branch or at the A/B split, and the header keeps Publish v4 only. On phones it keeps neither, and the settings panel sits under the canvas.

Segments

Who opened, who clicked, who never replied.

Who opened, who clicked, who never replied.

  • 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.

Example dynamic segment, Pricing intent from paid search, in the rule builder. Where all of these are true: Pricing Viewed at least 2 times in the last 7 days, Channel (the first-touch channel) equals Paid search, and Has never had status Replied. A pill under the rules shows 32 profiles match. When the number of times, the time window or AND and OR changes, the pill shows Loading, then the new count: a preview of the rules, not live membership. A line under the builder puts the rules in words. On a narrow screen, the builder keeps the first two rules, and 36 profiles match.

Channels & inbox

The message goes out. The reply shows up on their profile.

The message goes out. The reply shows up on their profile.

  • 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.

Example app screens with a channel switcher. Inbox: the profile of Alex Moreau (alex@acme.com) at Acme shows your email and their reply in one conversation thread, with an answer drafted and ready to send. Its timeline shows the email_replied event with its properties and the received email, and a journey entry, Reply follow-up, is set to start on email_replied. Email: Resend connected as the default provider, a reply mailbox connected over IMAP, and the provider picker with Resend, SendGrid, Postmark, SMTP and Microsoft 365. SMS: a template that counts 115 characters and 1 segment, then 2 segments in Unicode once a curly apostrophe replaces the straight one, with Twilio, SMSPartner, MessageBird and HTTP API as providers. In-app: the snippet’s banner and modal on a sample page, for an identified visitor. Web push: one generic notification, for visitors who allowed notifications. Ad audiences: Meta, LinkedIn and Google audiences, each linked to a segment, synced when you click Sync now.

Results

Judge each journey by its goals.

Judge each journey by its goals.

  • 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.

Example results for the active journey Welcome series over the last 30 days. The period control also offers 7, 14 and 90 days. 812 entered, up 15.3% on the previous period. 89.2% completed, down from 98.3%, and 0.5% failed, down from 0.7%. The average duration is 2 days, down from 3. 182 enrollments, 22.4%, reached the goal node Activated. An A/B card for the split Welcome email covers the whole test, not the period: variant B winning, 97% confidence, +34% vs other. On its success metric, reaching the downstream node, A has 75 of 400 people (18.8%) and B 100 of 398 (25.1%). Email engagement is tracked too, with no winner. On a narrow screen, the A/B card shows the success metric only.

AI & MCP

Your AI, plugged in.

Claude CodeExample

Draft a welcome journey for new signups. Show me before publishing.

  • fromHellocreate_templateWelcome
  • fromHellocreate_journey_draftWelcome series, draft
  • fromHellopublish_journeyto be confirmed

Draft ready. Publishing takes a confirmation step.

The 59 MCP tools, grouped as playbooks and workspace context, segments, journeys, templates, tracking, analytics, people and approval.

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

Claude appClaude CodeCursorCodexAny MCP client

https://mcp.fromhello.io/v1

Journeys your agents build stay drafts until you publish them. MCP calls are never metered. No AI subscription? Team and up include AI credits for the built-in assistant.

How it all comes together. Six plays to grow your business.

Example data

Paid acquisition

Turn high-intent visitors into named leads.

Most high-intent visitors leave without a word. fromHello records the pages they view before you know who they are, and passes those page views to your Meta, LinkedIn or Google pixel. Your ad platform builds the audience from the pages you pick. When your ad brings them back and they sign up in the same browser, their earlier visits join their profile: the first click, the pages, the return visit. Anonymous visitors are tracked, never billed.

Illustration: an anonymous visitor reads your pricing page, then sees your ad, “Your trial is waiting.”, comes back and signs up as Alex Moreau.

Example data

How it runs

  1. StartsAn anonymous visitor reads your pricing and comparison pages, then leaves without signing up.
  2. ThenfromHello passes those visits to your Meta, LinkedIn or Google pixel. Your ad platform builds the audience from the pages you pick, and your ad brings them back.
  3. EndsThey sign up, and their earlier visits join their profile.

What you need

  • The fromHello snippet on your site and in your app, sharing one cookie domain, and an identify call at signup.
  • Your Meta, LinkedIn or Google pixel ID.
  • UTM tags on your ad links, so the return visit is tagged as a paid click.

Sales

Hand sales the trials that invited their team.

A trial that invites its team is telling you something. Write the rule once as a segment, for example: on a trial, 3 teammates invited and pricing viewed in the last 7 days. The first time someone matches, a webhook posts their name and company in your sales channel on Slack, and their whole history waits on their profile.

Illustration: Alex Moreau invites 3 teammates in your app and views pricing, enters the Product-qualified segment, and your #sales channel on Slack gets “Alex Moreau (Acme) is product-qualified.”

Example data

How it runs

  1. StartsA trial user has invited 3 teammates and viewed pricing in the last 7 days.
  2. ThenThey enter your product-qualified segment, and a webhook posts their name and company in your sales channel on Slack.
  3. EndsOne alert per person, the first time they qualify.

What you need

  • Your app sends team_member_invited and pricing_viewed.
  • Their name, company and plan on the profile, set from your app.
  • A Slack incoming webhook for your sales channel.

Expansion

Offer the upgrade when they hit the limit.

A plan limit is the best time to talk about the next plan. When your app reports the limit, an in-app message offers the upgrade. The next day, an email spells out their limit, read from the event itself. As soon as they upgrade, the journey stops.

Illustration: your app shows 5 of 5 seats used, an in-app message says “You’ve reached your plan’s limit.” with an Upgrade to Pro button, and the account is upgraded to Pro.

Example data

How it runs

  1. StartsYour app sends plan_limit_reached.
  2. ThenAn in-app message offers the next plan, and an email the next day spells out their limit.
  3. EndsAs soon as they upgrade and your app sends subscription_expanded.

What you need

  • Your app sends plan_limit_reached with the limit, and subscription_expanded when they upgrade.
  • An email template that quotes the limit.
  • The fromHello snippet in your app, with signed-in users identified, for the in-app message.

Payments

Recover failed payments before they cost a customer.

A declined card is rarely a customer who wants to leave. When Stripe reports a failed payment, your backend sends it to fromHello with the amount. An email asks them to update their card, an in-app banner repeats it, and an SMS follows on day 3. As soon as the payment goes through, it all stops.

Illustration: a card is declined, an email says “Your payment didn’t go through” for €49 on the Pro plan, with an Update card button, an SMS follows on day 3, and the payment goes through.

Example data

How it runs

  1. StartsStripe reports a failed payment, and your app sends payment_failed with the amount.
  2. ThenAn email with the amount and a link to update the card, an in-app banner, then an SMS on day 3.
  3. EndsAs soon as payment_succeeded arrives.

What you need

  • Your backend, or Zapier or Make, sends payment_failed and payment_succeeded to the fromHello API, with your own user ID for that customer.
  • A transactional email template.
  • The fromHello snippet in your app, with signed-in users identified, for the in-app banner.
  • An SMS provider and their phone number, for the day 3 reminder.

Retention

Turn cancellations into conversations.

People who cancel have a reason. Ask for it. When someone cancels, a short email from your own address asks what would have made them stay, with one follow-up a few days later. Their reply comes back to your mailbox and onto their Conversations tab, and it stops the journey, which cancels the follow-up.

Illustration: Alex Moreau cancels their subscription, you ask what would have made them stay, and they reply “We needed SSO for the whole team.”

Example data

How it runs

  1. StartsYour app sends subscription_cancelled.
  2. ThenA short email from your own address asks what went wrong, and one follow-up goes out a few days later if they haven’t replied.
  3. EndsWhen they reply, or after the follow-up. A reply stops the journey and waits on their profile.

What you need

  • Your app sends subscription_cancelled.
  • Your mailbox connected for sending and replies: Microsoft 365, or SMTP with IMAP.

Reviews

Ask your promoters for a review while they’re still glowing.

A 9 out of 10 is an invitation. Ask for the review. When your app records a score of 9 or 10, an email thanks them and links to your review page, with one follow-up. Lower scores can start a second journey that alerts your team in Slack instead.

Illustration: a customer answers 9 to “How likely are you to recommend us?”, then gets an email, “Glad it’s working for you.”, asking for a review, with a follow-up on day 5.

Example data

How it runs

  1. StartsYour app sends nps_submitted with a score of 9 or 10.
  2. ThenAn email thanks them and asks for a review, with one follow-up.
  3. EndsAfter the follow-up, or as soon as fromHello records a click from them.

What you need

  • Your app sends nps_submitted with the score.
  • The link to your review page.
  • For the low-score alert, a Slack incoming webhook.

fromHello is built by Synapsr, the studio behind Pelli and Louez.

Over 7,000 photographers deliver their photos with Pelli.

Shipped lately

  1. First-party open tracking

  2. See who is in each journey

  3. Microsoft 365 mailboxes

Hosted by us, or on your servers. Two ways to run it.

Recommended

fromHello Cloud

Nothing to install. Nothing to upgrade.

Join the waitlist
Recommended

fromHello Cloud

Nothing to install. Nothing to upgrade.

We run Postgres, Redis and every upgrade, and support is included. From Team up, email sending is set up for you and AI credits are included.

  • Hosted for you
  • We run Postgres, Redis and every upgrade
  • Email sending, set up for you (Team and up)
  • AI credits (Team and up)
  • Support included

Every contact, event and message is readable as JSON through the API. When you self-host, all of it sits in your own Postgres.

Data and control, either way

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.
Join the waitlist
AGPL-3.0

Self-host

Run it yourself. With or without us.

Your own servers run Postgres 18+, Redis 8+, an API, a worker, the dashboard and an optional MCP server. You run upgrades and backups, and help comes through GitHub issues.

  • On your own servers: an API, a worker, the dashboard and an optional MCP server
  • You run Postgres 18+, Redis 8+, upgrades and backups
  • Your sending provider: Resend, Postmark, SendGrid, SMTP or Microsoft 365
  • Your AI key, or local models through Ollama
  • Help through GitHub issues

With your own SMTP server and Ollama, your data can stay entirely on your servers.

Every contact, event and message is readable as JSON through the API. When you self-host, all of it sits in your own Postgres.

Data and control, either way

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.
Self-hostingView on GitHub (opens in a new tab)

Data and control, either way

  • Export and erase
  • Automatic suppression
  • Audit log
  • Workspaces and roles
  • Your sending domain
  • First-party tracking

One price, set by your contacts. Seats and events never add to it.

  • Core

    Up to 20,000 contacts Month-to-month

    From €39 a month

    • Your own email and SMS providers
    • AI over MCP, with your own assistant
    • Unlimited seats

  • Team

    Up to 20,000 contacts Month-to-month

    From €59 a month

    • Everything in Core, plus
    • 25,000 emails a month
    • 1,000 AI credits a month

  • Business

    Up to 200,000 contacts 12-month term

    From €299 a month

    • Everything in Team, plus
    • 5,000 AI credits a month
    • 3 workspaces

  • Enterprise

    Up to 1,000,000 contacts 12-month term

    From €1,690 a month

    • Everything in Business, plus
    • 20,000 AI credits a month
    • 10 workspaces
Join the waitlist

Prices in euros, excluding VAT. SMS through your own provider. Self-host: AGPL-3.0, unlimited contacts.

Above 1,000,000 contacts? Talk to us.

Compare plans

One meter: the contacts you can reach.

Plan details

Plan details for Core, Team, Business and Enterprise
CoreTeamBusinessEnterprise
From€39a month€59a month€299a month€1,690a month
ContactsUp to 20,000Up to 20,000Up to 200,000Up to 1,000,000
TermMonth-to-month12-month term, billed monthly
Email a monthYour own provider10× your contacts10× your contacts8× your contacts
AI credits a monthYour own assistant, over MCP1,0005,00020,000
Workspaces11310
SupportEmailEmailPriorityPriority and onboarding
SeatsUnlimited, on every plan
ChannelsEmail, SMS, in-app, web push, ad audiencesOn every plan. SMS through your own provider.

  • Core

    From €39 a month

    Contacts
    Up to 20,000
    Term
    Month-to-month
    Email a month
    Your own provider
    AI credits a month
    Your own assistant, over MCP
    Workspaces
    1
    Support
    Email

  • Team

    From €59 a month

    Contacts
    Up to 20,000
    Term
    Month-to-month
    Email a month
    10× your contacts
    AI credits a month
    1,000
    Workspaces
    1
    Support
    Email

  • Business

    From €299 a month

    Contacts
    Up to 200,000
    Term
    12-month term, billed monthly
    Email a month
    10× your contacts
    AI credits a month
    5,000
    Workspaces
    3
    Support
    Priority

  • Enterprise

    From €1,690 a month

    Contacts
    Up to 1,000,000
    Term
    12-month term, billed monthly
    Email a month
    8× your contacts
    AI credits a month
    20,000
    Workspaces
    10
    Support
    Priority and onboarding

On every plan

Seats
Unlimited
Channels
Email, SMS, in-app, web push, ad audiencesSMS through your own provider.

Every size

Per month, by the contacts you can reach.

Core

Month-to-month

2,500 contacts
€39
5,000 contacts
€59
10,000 contacts
€89
20,000 contacts
€139

Team

Month-to-month

2,500 contacts
€59
5,000 contacts
€89
10,000 contacts
€139
20,000 contacts
€219

Business

12-month term, billed monthly

30,000 contacts
€299
50,000 contacts
€449
75,000 contacts
€599
100,000 contacts
€749
150,000 contacts
€999
200,000 contacts
€1,290

Enterprise

12-month term, billed monthly

300,000 contacts
€1,690
500,000 contacts
€2,490
750,000 contacts
€3,290
1,000,000 contacts
€3,990

Above 1,000,000 contacts? Talk to us

How we count

  • We count billable contacts as a daily mean.
  • Deleted, anonymous and suppressed contacts never count.
  • Never metered: seats, events, API and MCP calls, journeys, segments.
  • Over your size, extra contacts are billed per 1,000, with a prompt to upgrade, never automatically.
  • Extra email on Team and up: €0.20 per 1,000.
  • A year paid upfront costs 10 months.
  • Prices in euros, excluding VAT.

Self-host: AGPL-3.0, unlimited contacts. Yours to run, with or without us.

Join the waitlist

Core

Up to 20,000 contacts, month-to-month.

Size

Price by size

Per month, by the contacts you can reach.

2,500 contacts
€39
5,000 contacts
€59
10,000 contacts
€89
20,000 contacts
€139

fromHello Cloud · Core

Month-to-month

2,500 contacts
€39
Email through your own provider
Your provider
AI over MCP, with your own assistant
Your assistant
Unlimited seats
Included
1 workspace
Included
SMS, in-app, web push, ad audiencesSMS through your own provider
On every plan
Events, API and MCP calls, journeys, segments
Never metered
Anonymous, deleted and suppressed contacts
Never counted

Total €39 a month excluding VAT

Over your size, extra contacts are billed per 1,000, with a prompt to upgrade.

Join the waitlist

Team

Up to 20,000 contacts, month-to-month.

Size

Price by size

Per month, by the contacts you can reach.

2,500 contacts
€59
5,000 contacts
€89
10,000 contacts
€139
20,000 contacts
€219

fromHello Cloud · Team

Month-to-month

2,500 contacts
€59
25,000 emails a month
Included
1,000 AI credits a month
Included
Unlimited seats
Included
1 workspace
Included
SMS, in-app, web push, ad audiencesSMS through your own provider
On every plan
Events, API and MCP calls, journeys, segments
Never metered
Anonymous, deleted and suppressed contacts
Never counted

Total €59 a month excluding VAT

Extra email €0.20 per 1,000. Over your size, extra contacts are billed per 1,000, with a prompt to upgrade.

Join the waitlist

Business

Up to 200,000 contacts, 12-month term, billed monthly.

Size

Price by size

Per month, by the contacts you can reach.

30,000 contacts
€299
50,000 contacts
€449
75,000 contacts
€599
100,000 contacts
€749
150,000 contacts
€999
200,000 contacts
€1,290

fromHello Cloud · Business

12-month term

30,000 contacts
€299
300,000 emails a month
Included
5,000 AI credits a month
Included
Unlimited seats
Included
3 workspaces
Included
SMS, in-app, web push, ad audiencesSMS through your own provider
On every plan
Events, API and MCP calls, journeys, segments
Never metered
Anonymous, deleted and suppressed contacts
Never counted

Total €299 a month excluding VAT

Extra email €0.20 per 1,000. Over your size, extra contacts are billed per 1,000, with a prompt to upgrade.

Join the waitlist

Enterprise

Up to 1,000,000 contacts, 12-month term, billed monthly.

Size

Price by size

Per month, by the contacts you can reach.

300,000 contacts
€1,690
500,000 contacts
€2,490
750,000 contacts
€3,290
1,000,000 contacts
€3,990

Above 1,000,000 contacts? Talk to us

fromHello Cloud · Enterprise

12-month term

300,000 contacts
€1,690
2,400,000 emails a month
Included
20,000 AI credits a month
Included
Unlimited seats
Included
10 workspaces
Included
SMS, in-app, web push, ad audiencesSMS through your own provider
On every plan
Events, API and MCP calls, journeys, segments
Never metered
Anonymous, deleted and suppressed contacts
Never counted

Total €1,690 a month excluding VAT

Extra email €0.20 per 1,000. Over your size, extra contacts are billed per 1,000, with a prompt to upgrade.

Join the waitlist

Good to know. Price, data, the AI and running it yourself.

The questions people ask first.

  • What is fromHello?

    fromHello is open-source marketing automation: first-party tracking, real-time segments and journeys triggered by what people do, 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.

  • What happens after I join the waitlist?

    When you join the fromHello waitlist, the page confirms right away that you’re on the list, and fromHello emails you when your spot opens. Early access comes in stages, with hands-on onboarding: we help you get set up and bring your contacts over.

  • What does fromHello cost? Can I pay monthly?

    fromHello Cloud starts at €39 a month, excluding VAT, for up to 2,500 contacts on Core, and every plan can be paid monthly. Core uses your own email and SMS providers and AI over MCP; Team, from €59, adds bundled email and AI credits. Both are month-to-month, up to 20,000 contacts. Business and Enterprise run on a 12-month term, billed monthly. Deleted, anonymous and suppressed contacts never count. Self-hosting is AGPL-3.0, on servers and providers you run and pay for.

  • Do you have a startup program?

    Yes. Startups under two years old with less than €5M raised can apply for 12 months of Core on us, up to 20,000 contacts, with hands-on onboarding. See the startup program.

  • Does the AI send anything without my approval?

    No AI tool in fromHello sends a message, but AI actions can change live journeys without a confirmation step. A journey your AI agents build stays a draft until it is published. Publishing, pausing or deleting through an agent takes a confirmation step in your AI client. Other edits, such as changes to a segment or a template, apply when saved. Opt-in send-time personalization rewrites each email without per-message review. If the AI fails, the send waits by default.

  • Where is my data stored?

    On fromHello Cloud, your data sits in the Postgres we run; self-hosted, in your own, and with your own SMTP server and Ollama it can stay entirely on your servers. The services doing the work receive what they need: the providers sending your email and SMS, the AI model and ad platforms. Export a contact as JSON, or erase their profile and messages, through the API. Every erasure is audit-logged. Unsubscribes and bounces feed a suppression list, checked before every send.

  • Can I move from my current tool to fromHello?

    Your contacts can move to fromHello as a CSV with custom fields, or through the API along with past events, dated as they happened. Segments, templates and journeys are rebuilt rather than imported. Opt-outs, consent records and message history don’t import, so leave anyone who unsubscribed, bounced or complained out of the file. During early access, we help you get set up and bring your contacts over. fromHello publishes comparisons with other tools.

  • What’s the difference between fromHello Cloud and self-hosting?

    fromHello Cloud is hosted for you, and we run Postgres, Redis and every upgrade; from Team up, email sending is set up and AI credits are included. Self-hosted under AGPL-3.0, fromHello runs on your own servers: you run all of it and bring your own email provider and AI key, or local models through Ollama. Either way, SMS goes through your own provider, and your own AI agent can connect over MCP.

  • Can I run fromHello myself, or get my data out?

    Yes: fromHello is open source under AGPL-3.0, and you can run it on your own servers, with unlimited contacts. On fromHello Cloud, your contacts, events and messages read out as JSON through the API. Self-hosted, they sit in your own Postgres, and pg_dump takes the whole database.

Early access

fromHello Cloud

You didn’t start this to stay small.

Early access to fromHello Cloud opens in stages. Onboarding is hands-on: we help you get set up and bring your contacts over.

We’ll email you when your spot opens. No spam.

Not ready to join? View on GitHub