The useful thing about a postman is that he already knows where you live. In India, that familiar route can carry something besides letters: access to banking. India Post Payments Bank uses an assisted model in which postal workers and agents bring financial services to customers. Behind part of that experience sits Appzillon, software made by i-exceed. The technology travels the last mile in someone else’s hands.
- Appzillon supplies banking applications and the tools to build them.
- Its customers span corporate banks, retail institutions and assisted banking networks.
- The practical idea: let customer journeys change independently of the core.
That is a more interesting starting point than another photograph of a phone displaying a balance. Digital banking has two separate challenges: making services available and making them usable. A customer may need an agent, a business may need several approvals, and a bank may need to connect the whole encounter to systems built long before smartphones. i-exceed works in those connections.
The people who knew what sat underneath
The company began in 2011. Joseph John, Sundararajan S and Kapil Gupta had worked at i-flex, the banking-software business associated with FLEXCUBE. They came to mobile banking with experience of the machinery behind it. Their opportunity was becoming visible in everyday life: people were carrying increasingly capable computers in their pockets, and expecting established businesses to keep up.
In an interview republished by the company, Sundararajan explained the initial decision: “We began investing in mobile-based technologies because it was the logical bet with the proliferation of devices.” The observation sounds ordinary now. The engineering choice underneath it was consequential: how much of a bank’s mobile future should depend on its existing core?
Omdia’s account identifies the constraint. Mobile capabilities were often tightly tied to core banking products. Separate teams also built for different operating systems. Appzillon aimed to loosen that coupling and reduce duplicated development. Omdia dates the digital banking platform’s launch to 2013. The early problem was structural: the front door could be difficult to change because of what stood behind it.
Buy the journey. Build the difference.
Today, Appzillon combines a low-code development platform with prebuilt banking solutions. A bank can start with established journeys for opening accounts, moving money or serving business customers, then adapt them. It can also use the platform to develop its own applications. That combination matters because banks rarely want every interaction to be a fresh engineering project.
The vocabulary is technical but the purpose is legible. Microservices divide functionality into smaller services. APIs connect applications and systems. A headless approach separates presentation from the services underneath. Cloud-native infrastructure supports deployment and scaling. Together, those ideas describe the MACH architecture i-exceed promotes. Low-code tooling and a shared codebase are intended to reduce repeated work across devices.
Its place in the market is therefore fairly specific: digital engagement and application delivery for financial institutions. Alternatives include Backbase, Temenos, Infosys Finacle and Oracle’s digital banking offerings, alongside internal development. Architectural language alone does not distinguish Appzillon; other vendors use similar approaches. The more useful distinction is the combination of banking-specific journeys, development tooling and experience across very different service channels.
A corporate treasurer and a postal worker
Consider corporate onboarding. Opening services for a company involves a different set of relationships and documents from opening a personal account. i-exceed lists Citi among its customers, and Omdia reports an Appzillon engagement beginning in 2018 for corporate client onboarding. This is the administrative territory where better software can remove repeated requests and disconnected handoffs, rather than merely repaint a dashboard.
At the other end sits India Post Payments Bank. In September 2024, i-exceed described its contribution to IPPB reaching 100 million customers. Its account emphasised assisted services, multilingual interfaces and operation in areas with unreliable connectivity. The distinction is worth keeping: that figure belongs to the bank’s customer base. Appzillon is one technology contributor within a much larger distribution and banking operation.
Reported by i-exceed’s current website. A measure of institutional reach, not a count of interchangeable deployments.
A third example makes the range tangible. Canara Bank’s CANDI digital branch used Appzillon for account opening and other services. The company’s account describes Aadhaar-based onboarding with biometric, iris or one-time-password authentication. Here, the branch remains part of the experience. The software changes what happens inside it. Across these examples, the channel follows the customer’s circumstances.
The work after the demo
i-exceed sells to institutions through a B2B software model, with platform and application licensing or subscriptions, implementation and consulting. Partners extend its reach. Mambu brings a SaaS core banking proposition; Finastra has worked with i-exceed around corporate onboarding and distribution. For a buyer, the relevant purchase is a functioning banking journey connected to the institution’s operating environment.
The sensible cost calculation includes integration, migration, testing, infrastructure, security review and support. Low-code reduces some development work; it does not remove those obligations. A bank evaluating Appzillon should choose one consequential journey, establish the current completion time and abandonment rate, and test who can maintain the resulting application. A convincing demonstration should survive contact with real documents, exceptions and approval chains.
That also explains the conditions for a useful deployment. The bank needs accessible underlying services, agreed ownership of customer journeys and people able to govern changes. A faster interface cannot, by itself, accelerate an unavailable system or settle an unresolved approval policy. These are practical implications of connecting software to banking operations, rather than promises about any particular implementation.
The channel follows the customer’s circumstances.
The next queue is made of documents
The product line now includes Appzillon X AI, advertised for guided onboarding, conversational experiences, document summarisation and other banking workflows. Appzillon Labs offers pilots and innovation sprints. These are propositions to evaluate, with performance established in the bank’s own environment. The most useful tests remain concrete: fewer repeated tasks, clearer decisions and a customer who can complete the job.
The postal route supplies a good final test. The customer need not understand microservices, recognise i-exceed or own the newest phone. Someone has arrived with a way to get something done. For banking software, that is a demanding definition of success: the elaborate machinery becomes useful at an ordinary doorstep.