Two deployment shapes, one India data plane
Reconciliation infrastructure has to fit the customer's operating envelope, not the other way around. A listed manufacturer's board, a fast-growing NBFC's CTO, and a CA firm's partner team all need different control surfaces over the same engine.
TransactIG is delivered in two deployment tiers — managed India cloud on AWS Mumbai and dedicated private tenant. On-premise is deliberately not offered: both tiers keep customer data inside the India data plane on the same audited, continuously patched infrastructure, with a faster upgrade cadence than a self-operated data centre allows.
This page describes the two shapes, the typical fit profile for each, and the 2-4 week go-live customers should expect regardless of tier.
The two deployment tiers
Same engine, same variance taxonomy, same audit trail. What differs is who provisions and operates the substrate underneath — and the data-control bar the customer needs to meet.
Managed India cloud
Fully managed on AWS Mumbai 2-3 week go-liveA multi-tenant managed service operated by Terra Insight on AWS Mumbai (ap-south-1). Logical tenant isolation at the data layer, per-tenant configuration of industry preset, tolerance bands, and integration mappings. Terra Insight owns uptime, patching, scaling, and incident response under MSA-documented SLAs. The fastest path from evaluation to production.
- ▸ Finance teams that want the engine without operating the infrastructure
- ▸ Mid-market manufacturers, NBFCs, and platform businesses optimising for go-live speed
- ▸ Customers where contractual SLAs from a vendor are preferable to in-house reliability burden
- ▸ Pilot-stage partners validating production fit before deciding on a longer-term tier
- ▸ Multi-tenant logical isolation with tenant-specific configuration
- ▸ Terra Insight owns uptime, patching, scaling, and incident response
- ▸ Managed upgrade cadence coordinated with customer change windows
- ▸ Documented SLAs in the Master Service Agreement
Private tenant
Dedicated single-tenant on AWS Mumbai 3-4 week go-liveA dedicated single-tenant instance on AWS Mumbai with isolated compute and storage. Terra Insight operates the deployment; the customer holds a dedicated data plane with no cross-tenant shared infrastructure. Customer-specific networking posture, identity-provider integration (SAML, OIDC), and change windows. The right shape when multi-tenant isolation does not meet a board, auditor, or regulator expectation — without taking on the operational burden of on-premise infrastructure, which TransactIG deliberately does not offer.
- ▸ Enterprise finance teams whose boards or auditors require dedicated infrastructure
- ▸ Listed entities and regulated NBFCs with strict single-tenant isolation requirements
- ▸ Volume or customisation profiles that exceed the managed-tier envelope
- ▸ BFSI and regulator-mandated customers who need isolation but not a self-operated data centre
- ▸ Dedicated data plane with no cross-tenant shared infrastructure
- ▸ Customer-specific networking, identity integration (SAML, OIDC), and change windows
- ▸ Dedicated incident-response paths and named operational contacts
- ▸ Terra Insight owns patching and upgrade cadence — no customer-side infrastructure team required
India data residency, every tier
Across both deployment tiers, customer data stays inside the India data plane. No statement, no ledger extract, no reconciliation output ever leaves the country. RBI IT governance direction on data localisation is met by architecture, not by process. See the security sub-page for the full control surface.
AWS Mumbai (ap-south-1) for compute, storage, and backup. No cross-region replication outside India. Operational metadata used to administer the service is itself held in-country.
Every TransactIG tenant runs on the same audited, continuously patched AWS Mumbai infrastructure. The dedicated private tenant satisfies the data-residency and regulator mandates that would otherwise call for on-premise, without the maintenance burden of customer-operated infrastructure.
No bank statement, no ledger extract, no reconciliation output, no variance report ever leaves the country. The India-data-plane guarantee is met by architecture, not by policy text.
RBI Master Directions on Outsourcing of IT Services and IT Governance — data localisation, vendor due-diligence, exit management, and incident reporting — shape how the service is delivered to BFSI customers across every tier.
2-4 week go-live, regardless of tier
The go-live timeline is consistent across tiers because the work is the same shape — source-system access, field mapping, industry-preset selection, reconciliation logic configuration, parallel run, cutover. The 24+ industry presets are why customers do not spend months in blank-engine configuration. See the integrations sub-page for connector coverage.
Source-system access
ERP read access, bank file delivery (SFTP / S3 / direct API), GST portal token handover, and where applicable platform settlement report access. Same work whether the engine sits on the managed tier or a dedicated private tenant.
Field mapping and industry preset
One of 24+ industry presets is selected — manufacturer, NBFC, healthcare, IT services, retail, hotels — pre-loaded matching rules, tolerance bands, and variance taxonomy. Customer-specific field mappings against ERP and bank format are confirmed.
Reconciliation logic configuration
Tolerance bands, multi-pass matching sequence, variance-code mappings, and ERP writeback rules are tuned to the customer's close-cycle reality. Configuration is held as versioned artefacts, not ad-hoc dashboard clicks.
Parallel run and cutover
One full close cycle is run in parallel — the customer's existing process plus TransactIG, side by side. Variances are reviewed, edge cases caught, then cutover signed off jointly. No customer goes live without the audit-trail evidence of a successful parallel close.
How to pick a tier
Four practical factors decide which deployment shape fits the customer's operating reality. A scoping conversation with Terra Insight engineering usually resolves the choice in one session. The buyer's guide walks through the board and audit committee framing.
Data-control bar
The first question — does your board, regulator, or auditor require dedicated, isolated infrastructure rather than shared multi-tenant infrastructure? If yes, private tenant fits. If managed AWS Mumbai is acceptable, managed fits. On-premise is deliberately not offered — the private-tenant model is built to satisfy the same data-residency and regulator mandates that would otherwise push a buyer toward on-premise, without the operational burden. Most finance teams sit comfortably in the managed tier; listed BFSI and PSU customers typically need private tenant.
Engineering team shape
Neither tier requires the customer to carry a production SRE function — Terra Insight owns uptime, patching, and incident response on both. This removes a reliability burden that a finance team should not be carrying, which is also why TransactIG does not offer a self-operated on-premise tier.
Time-to-go-live priority
Managed is the fastest path — typical 2-3 week go-live. Private tenant adds infrastructure provisioning and customer-side approval steps and typically settles at 3-4 weeks. The work shape is the same across both tiers; the difference is the isolation level of the substrate underneath.
Exit posture
Both tiers carry contractual exit clauses with documented data and configuration extraction. The exit pathway is contractually defined for either tier, not a goodwill negotiation at term end. This matches the RBI guidance on concentration risk and the audit-defensible posture customers' boards require.
Upgrade cadence and change windows
Reconciliation infrastructure cannot be upgraded inside a close cycle. Every tier of TransactIG carries an upgrade cadence shaped by who owns the substrate — and no customer is ever forced into an upgrade window inside their statutory close, statutory audit, or quarterly reporting freeze.
Managed tier
Upgrade cadence is coordinated with the customer change window. Quarterly minor releases land in pre-announced windows; security patches inside the documented SLA. No upgrade is forced inside a close cycle.
Private tenant
Dedicated change windows. Upgrade cadence is negotiated per tenant. Identity-provider changes, network posture changes, and major version upgrades all run through the customer change-management process — Terra Insight applies them, the customer schedules them.
Exit posture — contractual portability, every tier
At contract end, every TransactIG customer receives a documented extraction of their reconciliation data, configurations, variance-taxonomy mappings, and audit trail. The exit pathway is contractually defined — not a goodwill negotiation at the end of a term.
Reconciliation data extraction
Complete extract of matched and unmatched transactions, variance classifications, audit-trail records, and writeback evidence in open formats (CSV, Parquet). No proprietary lock-in on the data side.
Configuration export
Industry-preset choice, tolerance-band settings, field mappings, variance-taxonomy customisations, and reconciliation logic rules exported as portable artefacts. Designed so a successor system can be configured against the same envelope.
Documented exit pathway
The exit clause is contractually defined, not ad-hoc — timelines, deliverables, and acceptance criteria are in the MSA. This addresses the RBI guidance on concentration risk and the audit-defensible escape velocity customers' boards require.
Ready to scope the right deployment tier?
A 45-minute deployment-fit conversation with Terra Insight engineering typically narrows the choice to the right tier and surfaces any board, auditor, or regulator constraints that affect it.