About
Why we're building GetFluxly.
GetFluxly is product analytics, unified customer profiles, lifecycle automation, and email, all connected to the same customer record and to the email provider your team already uses.
Why we're building this
Most teams that try to get product analytics and lifecycle email right end up running three or four tools that don't share a customer record. An analytics product over here. A messaging product over there. An email sender bolted on. Identity stitched together by a half-broken sync job.
The result: behavior data and email outcomes live in different systems. The customer record is incomplete. Engineering owns the integration mess; growth owns the missed lifecycle moments; nobody owns the deliverability.
GetFluxly is what we wanted instead. One way to capture product behavior across browser and server. One profile model that holds anonymous and identified activity. One automation layer that reads behavior and triggers messages. Lifecycle email goes out through the provider your team connects (Amazon SES, Mailgun, SMTP2GO, and similar), so deliverability and pricing stay with your existing email setup instead of with us.
What's different
- One profile, end to end. Anonymous activity captured in the browser links to the same profile when you identify the user. Server events from your backend land on that profile too. Automation runs against it. Email outcomes feed back into it.
- Works with your email provider. Lifecycle messages go through Amazon SES, Mailgun, SMTP2GO, or any major email provider you connect. Deliverability and pricing stay with your existing email setup.
- Built for engineering teams. A clean HTTP Events API plus a JavaScript SDK. Easy to integrate, easy to debug, easy to operate alongside the rest of your stack.
- One vendor, fewer integrations. Replaces the stitched stack of analytics + ESP + reverse-ETL with a single event pipeline.
Who's behind it
GetFluxly is being built by a small founding team that's spent years writing product code that needed a CDP and lifecycle email and never quite found the right tool for engineering-led companies. We're still small on purpose. Every private beta customer talks to a founder directly.
Founder note coming soon. A more personal section with the founding team's names, backgrounds, and the specific moment that pushed us to start building this is in the works. In the meantime, if you want to know more before joining the beta, email hello@getfluxly.com and we'll reply.
Where to go from here
- Read the analytics docs to see how the SDK and Events API actually work.
- Browse copy-ready examples across React, Next.js, Vue, Node, Python, Go, and PHP.
- Apply for the private beta.