We built the transaction layer every neobank was rebuilding from scratch
Daniel Okonkwo had spent the previous two years doing data infrastructure work for fintech teams in Tampa. Over that time, he watched three separate neobank engineering teams each spend their first sprint or two building the same transaction category model from scratch, each one solving the same edge cases, each one shipping something fragile. In 2024, he started Openaggr to build that layer once and make it something teams could integrate in a day, not a quarter.
Three people, one narrowly focused product
Spent two years doing data infrastructure work for fintech teams in Tampa before founding Openaggr. Watched three separate engineering teams each rebuild transaction categorization from scratch and decided the layer needed to exist as a shared API.
Background in consumer finance product design. Focused on making the Openaggr taxonomy and response schema something product teams can use directly without a transformation layer.
Owns the enrichment pipeline, inference latency, and SDK releases. Previously worked on real-time data processing at a payment infrastructure company. Tracks p95 latency on every deploy and considers anything above 80ms a regression.
How we think about what we build
Get in touch
Tampa, FL 33602
Three people means every email goes to someone who can actually help. Integration questions, category taxonomy feedback, Scale plan discussions: reach out directly. No ticketing system, no auto-responder, no chatbot.
Contact form