Low-code integration platform for banking
Explore the risks and possibilities with a prompt for ChatGPT, Claude, or your agent.
Sandbox Banking built Glyue, a low-code integration layer for banks, credit unions, and fintech vendors. Founded in 2015 and admitted to Y Combinator's Winter 2017 batch, the company turned a failed universal-API idea into a configurable system for moving data among core banking systems, CRMs, loan platforms, files, and event streams.[1][2]
Its exit came from solving an awkward problem well. Banking integrations require local customization, but the adapters, templates, and controls created for one institution can still become reusable assets. That combination gave Glyue both services-like depth and software-like accumulation. nCino, a longtime partner with a larger distribution base, acquired Sandbox Banking in February 2025 and later relaunched Glyue as nCino Integration Gateway.[10][12]
Ravi Balasubramanian and Skye Isard arrived at bank infrastructure from finance and software. Balasubramanian studied electrical engineering and economics at Penn and Wharton, then worked at Lehman Brothers, Barclays, UBS, and Harvard Management Company. Isard studied at Tufts, worked at MIT's AI Lab, and also spent time at Harvard Management Company.[3][4] Public sources say they lived in the same house when they started the company, but do not establish how or when they first met.
The company emerged from a different product. The founders were selling financial-advisory software to banks and credit unions when integrations repeatedly slowed deployment. Isard later told Startup Boston, “The most concise way to put it is that we encountered the problem as we were trying to solve another one.”[3] The obstruction became the opportunity.
Their first answer was too ambitious and too shallow. “We thought at first that we should build an API to encompass all of banking – a kind of universal API – and that wasn’t exactly right,” Isard said.[3] A common interface sounded elegant, but banks needed integrations tailored to their systems, controls, and workflows. After landing an initial customer, the team spent about another year turning what it had learned into Glyue, a low-code builder that preserved institution-specific configuration.
Balasubramanian framed the broader market around specialization. In an Upstart interview, he described banking as a service as a model “for banks who say, we’re actually much better off focusing on a certain portion of what we do, which is servicing relationships.”[4] Fintech partners could supply other capabilities, provided somebody made the systems work together. That dependency became Sandbox Banking's market.
Glyue sat between a financial institution's systems and the vendors it wanted to use. A team could connect a core system, CRM, loan platform, data warehouse, or fintech service without writing every integration from scratch. The platform handled web APIs, scheduled extract-transform-load jobs, file and document transfers, webhooks, and Kafka-style event pipelines.[1]
The working unit was an integration assembled from adapters and endpoints. In Glyue's Integration Builder, implementers selected connectors, mapped fields, configured external destinations, set execution and data-retention behavior, and checked compatibility with the installed engine version. Permissions, comments, and tags made the work reviewable by more than one developer.[5] Separate governance reports showed who currently held access and kept a time-stamped ledger of grants, revocations, and group changes.[6]
This product design split the difference that the universal API had missed. Banks still received a custom integration, but Sandbox Banking could reuse adapters and templates across customers. Every new core connector or fintech solution expanded the catalog for the next implementation. The Upstart alliance showed the distribution benefit: Sandbox Banking could build one connection that moved loan and borrower data into bank core and CRM systems, then apply it across a larger partner base.[8]
The Plaid partnership extended the same pattern. Plaid supplied identity-verification data; Glyue moved it into Customer360 and other bank workflows.[9] By the acquisition, nCino said the platform connected at least 14 core systems with more than 50 financial-software products.[11]
Glyue's advantage was controlled flexibility. A bank could adapt the last mile instead of waiting for a core vendor to add a native connector. A fintech could reach several institutions through a maintained integration pattern. The governance layer mattered because the product moved sensitive data across organizational boundaries. Low-code reduced repetitive implementation work; it did not remove review, testing, or operational ownership.
Sandbox Banking sold into two linked groups. Banks and credit unions needed to connect legacy cores with newer customer, lending, and data systems. Fintech vendors needed a repeatable route into those institutions. The company named BankNewport, Silicon Valley Bank, United Bank, Choice Financial, and Service Credit Union among its customers in 2023.[7]
The range was wide. By March 2024, Sandbox Banking said its customers spanned institutions with $500 million to more than $200 billion in assets.[9] That breadth helped the catalog compound, but it also meant deployments crossed different cores, security practices, approval chains, and operating budgets.
No reliable public revenue-based market estimate for low-code bank integration was located. Institution counts give a defensible customer-pool boundary rather than a revenue forecast. At the end of 2025, the FDIC counted 4,336 insured commercial banks and savings institutions.[15] The NCUA counted 2,686 federal credit unions and 1,601 federally insured state-chartered credit unions.[16] Together, those figures describe 8,623 regulated institutions, although many would be too small, too consolidated, or already committed to other vendors.
Regulation also shaped demand. Joint federal guidance issued in 2023 requires banks to manage third-party relationships through planning, due diligence, contracting, monitoring, and termination.[13] The OCC's 2024 community-bank guide makes the trade-off explicit: vendors can add technology and distribution while reducing the bank's direct control and introducing risks that require active management.[14] Integration work therefore joins data mapping with evidence and governance.
Glyue competed with core vendors' native connectors, horizontal integration platforms, systems integrators, and internal bank engineering teams. Those options occupied different positions. Core vendors had privileged product access but weaker incentives to support every external service. Horizontal tools offered broad connector libraries but lacked bank-specific templates and controls. Consultants could manage exceptions, though their work did not automatically become reusable software.
Sandbox Banking's position combined product depth with ecosystem reach. Its 14-plus cores and 50-plus solutions created a useful catalog, while partnerships with Upstart and Plaid brought repeatable demand.[8][9] nCino had the stronger distribution advantage: it already sold a broad cloud platform to financial institutions and had worked with Sandbox Banking on integrations for years. The acquisition paired Glyue's connector assets with that installed base.
Public sources do not disclose Sandbox Banking's prices, revenue, gross margin, retention, or customer concentration. The product likely combined recurring platform access with implementation work, but the split cannot be established from available evidence. That gap matters because Glyue's economics depended on how quickly reusable adapters and templates reduced the labor required for each new institution.
The company reported $6 million in total financing after its 2023 round.[7] nCino first announced a $52.5 million cash purchase price, subject to adjustments, plus an earn-out opportunity of up to $10 million.[11] Its later SEC accounting recorded $53.5 million in final net cash consideration, $1.354 million of noncash consideration, and $8.1 million as the fair value of contingent consideration.[10]
The announced base cash price was 8.75 times reported financing. That arithmetic is not a valuation multiple or an investor return: the cap table, secondary transactions, dilution, debt, and payout allocation remain undisclosed. It does show that a company with modest published funding created an asset valuable enough for a public software buyer to internalize.
Sandbox Banking reported more than 70 financial-institution customers in February 2023.[7] At acquisition two years later, nCino said the total exceeded 100 institutions across North America.[11] The connector catalog had reached at least 14 core platforms and more than 50 software solutions.
The named relationships provide stronger evidence than a customer count alone. Upstart used Glyue to connect lending data across partner institutions. Plaid connected identity verification to bank customer workflows. BankNewport appeared both as a customer before the sale and as an endorser when nCino launched Integration Gateway afterward.[8][9][12]
Revenue quality remains unknown. Customer growth, product continuity, and the acquisition establish commercial relevance, while the public record does not reveal contract value, usage depth, churn, or profitability.
Sandbox Banking's post-mortem is an acquisition analysis. The company did not shut down after losing its market. It sold a working infrastructure layer to a strategic partner, and that partner kept the product alive.
The original universal API assumed that banks could conform to one common interface. Customer work showed the opposite: valuable integrations required institution-specific depth. The team responded by spending about a year after its first customer building Glyue, preserving customization inside a reusable builder.[3]
That correction changed the business mechanism. The reusable asset was no longer a universal data model. It was the accumulated catalog of adapters, templates, mappings, and governance patterns. Each implementation remained partly local, while its components improved the next one. The result supported more than 100 institutions by the acquisition.[11]
Selling to banks one at a time would have left Sandbox Banking with long enterprise cycles and repeated implementation work. Partnerships with Upstart and Plaid created a second path: connect a fintech once, then reuse the work across its institution network.[8][9]
The attempt worked, but it also exposed the strategic ceiling for an independent layer. The best distribution partners already owned larger customer relationships. nCino chief product officer Chris Gufford said in the 2025 announcement, “We’ve closely partnered with Sandbox Banking for years through many integration projects, so we’ve seen first-hand how this technology layer improves transparency, reduces integration friction, accelerates project timelines, and creates a hub for better data connectivity.”[11] A buyer with its own platform could spread Glyue across more workflows and capture the integration value inside a broader contract.
Bank integration is hard partly because the work cannot end at moving fields between systems. Institutions must control access, document changes, monitor vendors, and maintain a termination path. Federal guidance formalized that lifecycle while Glyue exposed permissions and a timestamped audit ledger.[6][13]
This complexity protected Sandbox Banking from generic connectors. It also rewarded vendors that could bundle integration with a larger regulated workflow. nCino's acquisition closed that loop. The earn-out could reach $10 million based on annual contract value, defined system connectivity, and specified product-development work, tying additional consideration to continued product expansion rather than a simple employee handoff.[10]
nCino relaunched Glyue as Integration Gateway seven months after announcing the acquisition.[12] The successor serves both financial institutions and fintech partners, preserving Sandbox Banking's two-sided position. Product continuity, customer count, and contract-based earn-out terms support a product acquisition reading.
The undisclosed economics limit stronger conclusions. nCino said Sandbox Banking's results were not material to its financial statements, and the public record provides no standalone revenue or margin. The outcome still reveals a defensible mechanism: deep customization can compound when the reusable layer is the tooling and evidence around each deployment, even when no universal interface can erase local differences.