Grow the sending lane without replacing the operating model.
Advanced Subscriber Intelligence is designed so organisations can move through the current Business and Professional capacity tiers without abandoning the platform, rebuilding the operator workflow, or buying a stripped-down product again under a different name.
The same ASI Core, protection rails, reporting evidence, interface logic, validation, compliance, Preflight, Queue Safety, provider pacing, and operational controls remain in place. Where a higher tier needs more server resources, the infrastructure is reviewed and uplifted through a controlled change.
A larger licence increases the permitted capacity ceiling. It does not automatically prove that the sender, reputation, data, provider lanes, or infrastructure are ready to use that ceiling immediately.
Capacity-Led Licensing
Controlled Infrastructure Uplift
Evidence Before Higher Volume
Capacity can be licensed. Safe volume still has to be earned.
Moving to a higher tier may raise the daily operating ceiling and provide more infrastructure. ASI still checks whether domain and IP reputation, list quality, consent, provider behaviour, queue health, complaint pressure, bounces, and operational evidence support the higher volume.
What stays the same as the current platform grows
The capacity tier can change without replacing the protected ASI operating model.
The operator workflow
Campaign creation, audience selection, content review, Preflight, queueing, monitoring, reporting, and exports remain familiar.
ASI Core truth
SQL remains the authoritative Truth Engine for subscriber, campaign, consent, suppression, eligibility, queue, sending, and evidence state.
Protection rails
Validation, Draft Content Review, compliance, Preflight, Queue Safety, provider pacing, bounce handling, and suppression continue to govern the send.
Reporting evidence
Reports Builder, Event Stream, Recipient Drilldown, message traceability, CSV exports, and reporting contracts remain protected evidence rails.
Six current capacity lanes. One ASI operating model.
The current commercial platform spans Business and Professional server classes from 10,000 to 250,000 emails per day.
10,000, 25,000, and 50,000 emails per day
For organisations that need private sending infrastructure, the full ASI protection and reporting model, and a lower daily operating lane without paying according to subscriber count.
100,000, 150,000, and 250,000 emails per day
For higher-frequency commercial operations that require more infrastructure, stronger throughput capacity, earlier data-lifecycle planning, and the same protected ASI operating logic.
No subscriber tax: current ASI pricing is based on licensed daily sending capacity, not the number of subscriber records stored in the platform.
Review, prepare, uplift, prove.
A tier change is treated as a controlled operational change, not merely a new licence string pasted into a box.
Review the requirement
Confirm expected daily volume, campaign shape, provider mix, queue behaviour, data growth, reporting load, retention needs, and the reason for moving tiers.
Check the environment
Review CPU, memory, storage, database growth, worker capacity, validation throughput, bounce handling, monitoring, archive policy, and operational headroom.
Apply the controlled uplift
Apply the appropriate licence and complete any required infrastructure change during an agreed maintenance window. The exact work and disruption depend on the existing and target tiers.
Prove the higher lane
Increase operating volume under current warm-up, provider pacing, Preflight, Queue Safety, reputation, and evidence rules rather than jumping immediately to the new ceiling.
The platform stays familiar. The operating environment may need more muscle.
Scaling responsibly means acknowledging the infrastructure and operational changes created by higher volume.
Server resources
CPU, memory, storage, database capacity, worker counts, and service limits may need to increase with the licensed lane.
Data lifecycle
Higher volumes create more send, event, bounce, reporting, and evidence data. Packaging, archive, retention, and deletion plans may need to begin earlier.
Operational monitoring
Queue, worker, validation, storage, provider, bounce, and infrastructure monitoring becomes more important as the consequences of pressure increase.
Sending progression
A higher ceiling may require a controlled volume ramp, provider-specific pacing, or further proving before normal use at the new tier.
Growth should not trigger platform theatre.
Within the current Business and Professional platform, moving tiers should not require the client to abandon ASI and start again inside a different product family.
No artificial feature ladder
Core protection, sending, reporting, compliance, validation, and evidence functions are not deliberately removed from lower tiers to create an upgrade trap.
No subscriber-count penalty
The licence is based on daily sending capacity, not a tax that rises merely because the database contains more subscriber records.
No forced workflow replacement
Operators continue using the same underlying ASI workflow rather than being retrained on a separate premium edition.
No instant reputation upgrade
The new licence does not rewrite provider history or grant immediate permission to send at the higher volume.
500,000 and 1,000,000 per day are a separate 2027 enterprise architecture.
Moving from the current platform into ASI Enterprise Linux is not presented as a fifteen-minute licence uplift. It is a planned enterprise transition into a full Linux-native system with a separate implementation, migration, acceptance, and proving path.
Launching in 2027
Enterprise 500 and Enterprise 1000 are planned for 2027 and remain subject to full enterprise-scale testing.
Separate implementation
The move requires discovery, architecture, infrastructure preparation, data planning, migration, training, acceptance testing, and controlled go-live.
Same governing principles
SQL remains the Truth Engine, ASI Core owns all decisions, provider and safety rails remain protected, and reporting evidence stays authoritative.
Fifteen-week proving path
The planned enterprise implementation includes a fifteen-week warm-up and proving period before full enterprise capacity is treated as earned.
Upgrade before pressure becomes the normal operating condition.
The best time to discuss the next lane is before daily demand repeatedly sits against the current capacity, storage, queue, or operational ceiling.
Sustained volume growth
The operation regularly needs more daily capacity rather than experiencing one unusual campaign spike.
Queue or processing pressure
Validation, queue movement, sending, bounce handling, reporting, or evidence processing is approaching the planned headroom.
Data growth
The active database and evidence footprint require a stronger storage, packaging, archive, or retention plan.
Commercial planning
A known launch, acquisition, seasonal period, new client, commerce expansion, or campaign programme will materially increase future demand.
A controlled expansion.
The team keeps the ASI operating model, the infrastructure gains the required headroom, the licence reflects the higher lane, and volume rises under evidence-led protection.
Buying the same platform again.
Growth should not force the client through an artificial feature maze, a subscriber-count tax, a rebuilt workflow, or a shiny new edition that quietly discards the evidence and controls already in place.
Explore the surrounding ASI rails
Continue into ASI Pricing, Sending Engine & Queue Control, Email Warm-Up, Migration & Merger Tools, Campaign Reports & Insights, and Enterprise Linux 2027.
Raise the capacity without lowering the protection standard.
Request a private Sender Review to examine current daily volume, campaign growth, queue behaviour, provider mix, server headroom, data growth, archive requirements, warm-up evidence, and the right ASI lane for the next operating stage.