TL;DR
The GetFluxly private beta opens Monday, May 25, 2026. Accepted teams get three months of full platform access at no cost, with no credit card on file. The application stays open and we onboard in waves.
GetFluxly is one platform for product events, unified customer profiles, behavioral segmentation, lifecycle automation, and email send. One JavaScript SDK and one HTTP API drop into your stack. Plug in the email provider you already run, Resend, Mailgun, AWS SES, or any SMTP relay, and trigger email from real product behavior on day one.
iAlready on the waitlist? Sit tight, no action needed. We’re emailing the first wave of approved teams on Monday morning, US Pacific. Everyone else gets a welcome the day they’re accepted.
What’s shipping in the beta
Five primitives, one platform. Each one is in production, on the same customer record, behind one SDK.
01 · Track
Capture every signal
Auto-capture pageviews, clicks, and forms. Plus trusted server events via the HTTP API.
02 · Profile
Unified profiles
Anonymous browser activity stitches to identified users automatically.
03 · Segment
Group by behavior
Filter on events, traits, and time. Live counts. No SQL.
04 · Automate
Trigger from real events
Wait, branch, delay, exit. Flows run on the customer profile.
05 · Send
Ship the moment
Send through your provider. Outcomes flow back to the same profile.
Day-one extras the beta ships with
- Live event stream. Tail incoming events in the Console with
L to switch modes. - Replay automations against any historical profile to debug why a flow did or didn’t fire.
- GDPR-friendly defaults. Consent, DNT, GPC honored out of the box; auto-capture is opt-in per project.
Use the email provider you already run.Native sending from GetFluxly is coming after the beta. Until then, plug in the relay your team already operates.
Resend Mailgun Amazon SES Custom SMTP
What you get during the beta
Three months of full platform access, no card, no nag. We want real teams using the product against real volume, and we want feedback we can act on. In exchange you get every primitive at no cost, and beta members are grandfathered into whatever plans we ship later, with extra perks for the earliest cohort.
- Full Console, SDK, and HTTP API access. No feature gates.
- Direct line to the team in a shared Slack Connect channel.
- White-glove onboarding for teams shipping more than a few thousand events a day.
- Migration help when native sending lands, on the house.
How to get in
The application is one screen and takes about a minute. The more context you share about your use case and event volume, the faster onboarding goes. We’re prioritising teams with a SaaS product live (or close to it) and a clear lifecycle moment they want to instrument first: onboarding, activation, trial, or retention.
Prefer a conversation? Email hello@getfluxly.com and we’ll set up Slack Connect or a 15-minute call.
What’s coming after the beta
The next thing we’re shipping is native sending from GetFluxly, so you can run the whole loop without a separate ESP. Pricing finalises before the beta closes, and beta members get grandfathered plans. The roadmap from there: richer template editing, deeper deliverability tooling, and a first-party transactional API.
Watch the changelog for weekly drops, or follow @getFluxly for shorter updates.
FAQ
Do I need to bring my own email provider?
Yes, for now. Native sending from GetFluxly is in active development. Until it ships, plug in your own ESP (Resend, Mailgun, AWS SES, or any SMTP relay) and GetFluxly handles everything else. Beta members get a free migration when native sending lands.
What does it cost during and after the beta?
The private beta is free for the first three months. Pricing isn’t finalised yet, but it lands before the beta closes. Beta members are grandfathered into whatever plans we ship later, with extra perks for the earliest cohort.
How are subscribers counted?
A subscriber is an email address that has received at least one message from GetFluxly in the last 60 days. Anonymous events don’t count. Dormant contacts don’t count. Never-emailed profiles don’t count.
Is GetFluxly privacy- and GDPR-friendly?
Yes. Auto-capture is opt-in per project. Identification only happens when the SDK is told a real user is present with consent. Profile traits are editable and deletable per user; the primitives you need for subject access and erasure requests are there.
