Skip to main content
TransactIQ · Deployment

Managed on AWS Mumbai

TransactIQ is delivered as a managed service on Terra Insight's AWS Mumbai infrastructure with India data residency by architecture. Two tiers — shared multi-tenant and dedicated single-tenant private cloud — cover the isolation range Indian NBFCs and digital lenders require. Customer-owned cloud (BYOC / lender-VPC) and on-premise installation in a physical data centre are deliberately not offered.

Managed India cloud

Shared multi-tenant on AWS Mumbai

A managed service operated by Terra Insight on AWS Mumbai with India data residency by architecture. The lender integrates via API; Terra Insight handles infrastructure, patching, scaling, and incident response. The fastest path from evaluation to production and the default deployment shape for most NBFCs and digital lenders.

Right fit for
  • NBFCs and digital lenders without a dedicated SRE team
  • Teams optimising for go-live speed rather than infrastructure ownership
  • Lenders where contractual SLAs from a vendor are preferable to in-house reliability burden
  • Pilot-stage partners validating production fit before negotiating enterprise terms
Operational model
  • AWS Mumbai region with tenant-scoped logical isolation and per-tenant configuration
  • Terra Insight owns uptime, patching, scaling, incident response
  • SLAs documented in the Master Service Agreement
  • Managed upgrade cadence coordinated with customer change windows

Dedicated private tenant

Single-tenant on AWS Mumbai

A dedicated single-tenant instance on AWS Mumbai with isolated compute and storage. Terra Insight operates the deployment; the tenant retains dedicated resources. The right shape when a regulator conversation, board mandate, or group-IT policy requires infrastructure isolation beyond multi-tenant logical separation.

Right fit for
  • Enterprise NBFCs with strict single-tenant isolation requirements
  • Regulated entities whose boards or auditors require dedicated infrastructure
  • Lenders with volume or customisation profiles that exceed the shared managed tier
  • Group-IT policies that mandate isolated compute and storage per business unit
Operational model
  • Dedicated data plane on AWS Mumbai with no cross-tenant shared infrastructure
  • Customer-specific networking posture and identity integration options
  • Dedicated change windows, upgrade cadence, and incident-response paths
  • Contractual data-extraction and configuration-export clauses at contract end

How to pick a tier

Four practical factors to decide between shared managed and dedicated private tenant. A shared conversation with Terra Insight engineering usually resolves this in one session.

Isolation bar

If a regulator conversation, board mandate, or group-IT policy requires infrastructure isolation beyond multi-tenant logical separation, dedicated private tenant is the shape. Otherwise the shared managed tier meets the bar for the majority of NBFCs and digital lenders. Both tiers run on Terra Insight's AWS Mumbai infrastructure — customer-owned cloud (BYOC / lender-VPC) and on-premise installation in a physical data centre are deliberately not offered.

India data residency

Both tiers keep customer data inside the AWS Mumbai region by architecture. No statement or extracted signal leaves the India data plane. RBI IT governance direction on data localisation is met by the deployment itself, not by process.

Time-to-go-live

The shared managed tier is the fastest path — the integration window is days-to-weeks. Dedicated private tenant adds provisioning and networking-integration steps, typically extending the onboarding window by two to four weeks.

Escape velocity

Both tiers support documented data extraction and configuration export at contract end. Dedicated private tenant additionally provides a per-tenant snapshot of infrastructure state at handover.

Ready to scope the right tier?

A 45-minute deployment-fit conversation with Terra Insight engineering typically narrows this to the right tier and surfaces any operational constraints that affect it.

Request deployment-fit call