The platform in three parts

There is no fourth. Everything else Flowora does is one of these three answering a question about the other two.

Delivery engine

Connections held in our own name, a failover order you can read, and rejections that name the rule that caused them.

One primary and two fallbacks per market, ordered by measured delivery rather than price
Content-class rejections raised as their own event, so silent filtering stops being silent
Throughput shaped per network, because a burst is what gets a sender identity suspended

Every opt-in, its source, its timestamp and every change since, in one record the send path reads before it moves.

Import keeps original sources and dates rather than stamping everything with the migration day
Opt-out writes back within seconds and applies across every brand you run on the account
Export produces evidence in a form a data protection authority will accept unedited

Pick Dublin, Frankfurt or Toronto once. Message bodies and recipient numbers live there and are enforced there.

Residency is a storage-layer constraint, not a policy statement in a contract annex
Support tooling honours the same boundary, so an engineer cannot read data out of region
Retention runs to your schedule, with a documented floor for the records law requires

Being clear about the edges saves everybody a discovery call.

We do not hold your player profiles, segments or lifecycle logic. We read a list you send and a consent state we already hold.

Templates are yours. We will tell you which market will refuse one and why, and we will not write the offer.

Where a market can only be reached through an aggregator we say so on the coverage page rather than quietly buying it in.

You hold the operating licence in each market. We check it is current and refuse traffic where it is not.

Most operators start with the register because it is the piece an auditor asks about first, then move routes across market by market.