Home / Platform / SaaS or on-premise

SaaS or on-premise — Veengu deployment options.

Two deployment models, same platform. SaaS hosted by Veengu on AWS or Huawei Cloud, or on-premise inside the operator’s datacenter or private cloud. Trade-offs, fit criteria, and cost considerations.

Both deliver the same platform, the same APIs, the same back office. The choice depends on regulatory pressure, IT capacity, and operating preferences — not on which features are available.

Book a demo Send your scope

SaaS

AWS · Huawei Cloud

On-premise

Operator datacenter · Private cloud

Same platform · Same APIs · Same back office

Two deployment models

Same platform, two ways to run it.

Veengu ships in two deployment models. The choice depends on regulatory pressure, IT capacity, and operating preferences — not on which features are available.

Option · 01

SaaS deployment

Veengu operates the platform on its cloud account. The operator consumes the service via API and configures it via the operator back office. Veengu handles patching, monitoring, scaling, backups, and infrastructure incident response.

Time to live 4 to 8 weeks from contract to sandbox

Cost shape Recurring subscription dominates; implementation fee smaller

Operations Veengu owns infrastructure ops; operator owns business ops

Data residency Limited to AWS or Huawei Cloud regions Veengu serves

Updates Coordinated platform rollouts; tenants notified in advance

Fits Fits operators with no internal infrastructure team, startups optimising for time to live, and jurisdictions where SaaS for regulated fintech is accepted by the supervising regulator.

Option · 02

On-premise deployment

Veengu deploys the platform into the operator’s datacenter or private cloud. The operator runs day-to-day operations — monitoring, backups, patching, incident response — using its own toolchain. Veengu provides the platform, the upgrade path, and engineering support.

Time to live 10 to 16 weeks from contract to sandbox

Cost shape Higher implementation fee; subscription discounted vs. SaaS

Operations Operator owns infrastructure + business ops; Veengu provides L3

Data residency Wherever the operator runs the infrastructure

Updates Operator schedules upgrades; Veengu releases quarterly

Fits Fits licensed banks, operators with strict data-residency mandates (typically driven by central-bank regulation), and organisations with mature IT teams that already run regulated workloads on-premise.

Hybrid path

SaaS first. On-premise later. Same platform throughout.

A common path is SaaS-first, on-premise later. Operators launch on Veengu’s SaaS while they build out their IT and compliance capabilities, then migrate to on-premise when the regulatory or operational reasons require it.

Data and configuration migrate with the operator. The platform stays the same.

Migration path between SaaS and on-premise

Fig. · Migration path · SaaS → On-premise

Decision criteria

Which option fits your shape.

Quick decision rules. If more than one applies, the regulatory ones win.

→ On-premise If the regulator requires data residency in a specific country or on operator-controlled infrastructure.

→ SaaS If the operator has no internal IT team capable of running regulated infrastructure.

→ SaaS If time to live is the binding constraint.

→ On-premise If the operator already runs core banking on-premise and wants to integrate Veengu into its existing observability stack.

→ SaaS-first If the operator is unsure — SaaS first, with a documented migration path to on-premise built into the engagement.

Cost considerations

Comparable TCO over five years.

Total cost of ownership is roughly comparable across SaaS and on-premise over a five-year horizon. SaaS shifts more cost into the recurring subscription; on-premise shifts more cost into upfront implementation and ongoing infrastructure. Exact numbers depend on scale, modules, and integration scope — we quote against your specific shape.

Compliance boundary

The same boundary applies to both.

Veengu provides configurable KYC, AML-supporting workflows, audit trails, reporting tools, and integration capabilities. The licensed operator remains responsible for regulatory compliance decisions, monitoring policies, reporting obligations, and end-user outcomes — under both deployment models.

Your partner in financial innovation

The platform is the same. The control is yours.

A comprehensive software suite for different verticals in financial services, configurable to implement your vision with our platform and professional services. Build unique fintech solutions across the world with our modular, cloud-native platform.

Two deployment models. One platform contract.

Veengu empowers financial institutions with cutting-edge tech solutions. Build unique fintech offerings across the world with our modular, cloud-native platform.

Related platform capabilities

Discuss your deployment fit.

Bring your regulatory licence, target geographies, expected scale, and your IT team's operating model. We respond within three business days.

Book a demo Send your scope

SaaS or on-premise — Veengu deployment options.

Same platform, two ways to run it.

SaaS deployment

On-premise deployment

SaaS first. On-premise later. Same platform throughout.

Which option fits your shape.

Comparable TCO over five years.

The same boundary applies to both.

The platform is the same. The control is yours.

Two deployment models. One platform contract.

Other parts of the Veengu platform.

Core banking

System of record

White-label mobile apps

KYC orchestration

Card issuing

High availability

Discuss your deployment fit.