Industries · Finance
Credit unions, brokerages, wealth managers and fintechs need systems that hold up under audit. OlDevs builds secure portals, onboarding and KYC workflows, and the integrations that connect them to core banking and custodian platforms.
You own the code and IP Weekly demos Reply within one business day
Forecast engine
Demand forecast - next 8 weeks
94.2%
Accuracy
+18%
Vs baseline
8w
Horizon
Retrained nightly on 14 months of order behaviour.
OlDevs is a full-stack technology studio in Vancouver, British Columbia that builds software for credit unions, brokerages, wealth managers and fintech companies.The work usually covers secure client portals, onboarding and KYC workflows, document handling with e-signature, and integrations with core banking, custodian and payment systems. Every build is planned around audit trails, access control, disaster recovery and WCAG 2.2 AA accessibility, and clients own all code, designs, accounts and IP. To start a project, request a quote.
Key facts
Finance
The problems we are asked to solve most often — and how.
Applicants abandon accounts when identity verification, document upload and funding are spread across three disconnected tools. We rebuild onboarding as one guided flow with saved progress, clear status and a review queue staff can actually work through.
Core banking and custodian systems often expose batch files, nightly jobs or narrow APIs. We build an integration layer that normalises those feeds, handles retries and reconciliation, and keeps the client facing app fast while the core stays slow.
Statements, agreements and client instructions arrive by email and settle in shared drives. We build document handling with versioning, retention rules, e-signature and a record of who saw and signed what, so an audit request is a search rather than a scramble.
Advisors, branch staff, compliance officers and third party administrators all need different views of the same client. We design role and entitlement models up front, with delegated access, dual approval on sensitive actions and logs that show every change.
A portal clients use to move money cannot fail quietly. We plan for redundancy, tested backups, restore drills and a documented recovery runbook, then rehearse it, so an incident follows a plan instead of a group chat at midnight.
Financial advertising sits inside disclosure and suitability rules, and reviewers reject the claims campaigns were built on. We put compliance review inside the publishing workflow, so approved language ships and nothing goes live unreviewed.
Process
Discovery
We map the accounts, products, roles and systems involved, and agree what data is in scope. Regulatory context is captured here so it shapes the design rather than blocking launch.
Architecture and design
Data model, integration approach, access rules and interface designs, reviewed together. You see clickable screens before anyone writes production code.
Build in weekly increments
Short cycles ending in a working demo. Security reviews, accessibility checks and integration tests run alongside the build rather than after it.
Testing and hardening
Load, failover and restore testing, plus penetration testing by a firm you choose. Findings are fixed and retested before anything reaches clients.
Launch and support
Staged rollout with monitoring, runbooks and an agreed support path. We stay available as products, rules and volumes change.
How we work
You work with the people writing the code. There is no account layer relaying questions, which matters when a compliance answer changes a data model on a Tuesday.
Each week you see the real system running, not a status deck. Compliance, operations and marketing can react while changes are still cheap to make.
We document how data is stored, who can reach it and what is logged, then review those choices with your risk people during the build instead of presenting them at the end.
Audit trails, retention rules and access logs ship in the first release, not a later project. The reports your auditors and examiners ask for come out of the system itself.
Interfaces are built and tested to WCAG 2.2 AA, and we can build English and French side by side when you serve clients across Canada.
Code, designs, cloud accounts, analytics and IP are yours from the first commit, so you can bring the work in house or move it whenever you decide to.
Recommended
Since 2014
Building software from Vancouver
1 business day
Reply to every enquiry
WCAG 2.2 AA
Accessibility standard we build to
FAQ
Yes. We build for credit unions, brokerages, wealth and asset managers, insurers and fintech startups. We work inside the controls your compliance and risk teams set, and bring those people into design reviews early. We build the software and document the controls, but we do not provide legal or regulatory advice.
Usually yes. We start by reviewing what the platform actually exposes, whether that is a modern API, a scheduled file transfer or a vendor middleware layer. From there we build an integration layer handling authentication, retries, reconciliation and error reporting, so the client facing app stays fast and failures are visible instead of silent.
Data is classified at the start, then storage, encryption, access rules and retention are designed around that classification. Canadian work commonly involves PIPEDA and provincial privacy law, and Quebec Law 25 where Quebec residents are involved. We document what is collected, where it lives and who can reach it, and your counsel confirms the legal position.
Audit logging is part of the first release. Every meaningful action, who performed it, when, and what changed, is recorded so it can be queried and exported. We also build the reports internal audit and examiners request most often, so those requests are answered from the system rather than reconstructed by hand from spreadsheets.
Yes. We build native iOS and Android apps as well as web apps. Often we start with a responsive web app so one codebase serves everyone, then add native apps where biometrics, push notifications or offline behaviour justify them. The same security, logging and accessibility standards apply across all of them.
Yes. Our performance marketing work puts compliance review inside the publishing workflow, so approved language and required disclosures travel with each asset. We focus on measurement, landing pages and lifecycle messaging rather than claims reviewers will not clear, and your compliance team keeps final sign off.
You get monitoring, alerting and a documented runbook, plus an agreed support path with response expectations written down. Backups are tested by restoring them, not just scheduled. If an incident happens we work the runbook, communicate status as we go, and follow up with a written review and the fixes that came out of it.
Let’s connect
We’ll reply within one business day with next steps and a tailored quote — no obligation.