The email platform for PLG SaaS.

A lifecycle and transactional email platform for PLG SaaS. Ranla runs automations and audiences from product behavior, and includes a built-in agent that drafts and asks before it sends. SMS steps run through your Twilio account.

Small and mid-market PLG SaaS teams that need an email platform, not an agent to bolt onto mail they already send. If your last few thousand signups have never received an email from you, that is the job.

Yes, and most people start there. Connect GitHub and the agent scans the codebase, instruments the events Ranla needs, and opens a pull request you review. It can also recommend events you should add and write those into the same repo. If you already use PostHog, Amplitude, or Mixpanel, connect that instead. Ranla copies the moments that matter for people with an email, no PR required. Either path is enough.

Yes. Connect a GitHub repo in the workspace. The agent scans the product, recommends events you are missing, instruments them, and opens a pull request. You merge. It does not push to your default branch. Analytics connect is the other on-ramp if you would rather not change the repo.

No. Talk in the agent window. It can make templates, build campaigns, set up automations, and work audiences, the same place it can open a GitHub pull request. The dashboard is still there when you want it. Nothing sends until your rules say so.

Only if you tell it to. You pick the mode: Draft leaves everything for you to send, Propose asks before each send, Autopilot lets it send inside your limits. Any audience over 5,000 people needs your approval in every mode, and Ranla can tighten its own limits but never loosen them.

Yes. Ranla sits in Slack like a teammate. DM it, @mention it in a channel, or use /ranla. Brief it, approve a send, snooze, see what it is doing. Open the app when you want the canvas or the full picture.

You set the frequency cap, the daily account cap, and the audience size above which a send waits for you. They are enforced in the send path rather than asked for in a prompt, so they hold on every send. Defaults are two emails per person per week at least 48 hours apart, and sends stop mid-flight if complaints pass 0.1% or bounces pass 5%.

You pick the outcome that counts (activation, paid conversion, a first key action), and Ranla holds back a control group that gets nothing. Comparing the two is how you see whether a campaign moved that number or whether those users would have converted anyway. Campaigns that do not beat the control get dropped, and what does beat it shapes the next one, so the work compounds instead of repeating.

Both, in that order. Ranla starts with campaigns because that is how it finds out what works on your users, and a campaign that beats its holdout gets promoted, with your approval, into an always-on automation that fires for every user who hits that moment from then on. You can also ask it to build a standard automation outright, like a welcome sequence, a trial-ending series, or a win-back. Campaigns and automations share one frequency count per person.

You can see a draft written for your product in a couple of minutes without signing up. Real sends wait on setup finishing and on having something to segment on, usually the same day you connect analytics and pick moments, or merge the tracking pull request.

It can, through one API, sharing the same suppression list so a marketing unsubscribe never blocks a password reset. Transactional and lifecycle mail go out the same way.

Yes. Add the hosted MCP server (https://mcp.ranla.ai/mcp) in Cursor, Claude, Grok, or any client that speaks MCP. The agents talk to each other. Ranla still drafts and asks. Send rules and approvals stay in Ranla.

No. Other agents talk with the same Ranla agent that drafts and asks. Draft, Propose, and Autopilot still apply. Any audience over 5,000 people still needs your approval. Slack and the app still work.

Start sending for free. Paid plans start at $99/mo, priced on people engaged in the last 90 days (product use or email open/click), not raw list size. Each plan includes emails; usage above the included amounts bills as overage. SMS goes through your Twilio account.