Who is behind VEREA, and where it stands
VEREA is early. We would rather say that clearly than have you discover it three meetings in.
Who is behind it
Cris Naranjo, founder.
An engineer who has built software for more than a decade, the last nine years for London companies, mostly in fintech and insurtech, working on APIs, integrations and the infrastructure that runs them.
VEREA is a project of Naranjo Cloud LTD, a company registered in Cyprus, and is not yet a company of its own. The first markets are the United Kingdom, Spain and Portugal.
If you want to talk to the person who would build this, that is who replies. Write to hello@verea.dev.
Why we think this layer should exist
We do not think the answer to financial connectivity is one more aggregator. The aggregators are good, and there are plenty of them.
What is missing is the layer above them. A product team should be asking which financial capability it needs, not which vendor to marry. Today the second question wins, and the answer becomes load-bearing: schemas, consent flows, identifiers, error semantics and operational tooling all end up shaped by one supplier.
We want to make that choice reversible. Integrate once, and let the route underneath be a decision the infrastructure takes and reports, rather than an assumption baked into application code.
What stage we are at
The design partner programme is open. Before committing to a large engineering build we need to establish three things, because the honest version of this business depends on them being true.
Provider permission
Which upstream connectivity providers let a customer route its own contract and credentials through a service like VEREA, and which would permit VEREA to hold agreements itself.
Buyer demand
Whether senior product and engineering teams that already run connectivity as a platform dependency find the pain worth paying to remove.
Coverage differences
Where capability, completeness and behaviour actually differ when the same institutions are reached through more than one provider.
The order we intend to build in
Narrow first. A control plane that half works across everything is worth less than one that fully works across banking.
Banking first
Accounts, balances and transactions in the United Kingdom, Spain and Portugal. Three open banking environments, one useful cross-border story, one manageable launch surface.
Then wealth
Investments, positions, securities and pensions, reached through specialist providers rather than built connector by connector.
Then the wider graph
Liabilities, loans, mortgages and business finance, and governed access to all of it for software that acts on a customer’s behalf.
Talk to us early
The most useful conversation we can have right now is with a team that already runs connectivity across more than one provider. A connectivity audit is the shortest route into that conversation.