One platform. Your way.
OneApp Finance is API-first software for originating home-improvement loans. One headless Core is the single source of truth. Run the whole stack under your brand, bring your own front-end, or plug in just the pieces you need. You bring the capital and the brand; the platform is the software underneath.
One brain. One source of truth.
Underneath everything is a single headless Core that owns all state, all logic, all evidence, and every borrower communication. Any screen, whether ours, yours, or none at all, is a thin client that shows what the Core says and hands captured input back as evidence. Nothing important ever lives only in a front-end. That single rule kills the split-brain problem that sinks most origination stacks, where the portal and the loan system disagree and neither one is right.
- Same API for everyone. The public REST API plus signed webhooks is the exact same contract our own screens use. No private backdoors. Every caller goes through the same authorization, idempotency, and evidence rules.
- Operator-neutral by design. No products, rate cards, credit policy, or vendors come pre-seeded, so you never work around someone else's defaults. You set every business decision through a governed Config Studio, and that neutrality is the proof the program is yours.
- Built on capabilities, not vendors. The platform names a capability (bureau, KYC, e-sign, funding) and you pick the vendor that fills it. Swapping one for another is configuration, never a code change.
- The head never lies. A front-end never prices a loan, computes eligibility, or writes a decline reason. It renders what the Core returned. So a bug in a screen is a UX defect, never a compliance breach.
How it works
- The Core owns all state, logic, evidence, and borrower communications.
- One public REST API serves internal and external callers alike.
- Operator-neutral, so every business decision is yours to set.
RUN, EMBED, or ROUTE
One Core, adopted at three altitudes. Take the whole thing, take a few pieces, or use it to pass deals to other lenders. This is a separate choice from your operating model: decide what you run (direct, multi-lender, or hybrid), then how much of the stack you adopt (run, embed, or route).
RUN
Take the whole LOS: the Core, white-label borrower and dealer front-ends, and the operations console. Everything the homeowner and the rep touch wears your brand, not ours. This is the flagship setup.
EMBED
Keep your own experience and adopt only the parts you want: headless decisioning over the API, drop-in white-label components, or single widgets. A per-step ownership matrix and a strict evidence model keep delegated steps safe; the compliance-critical gates are always re-run by the Core itself.
ROUTE
Run intake, eligibility, and one soft credit pull, then fan the application out to other lenders, gather their offers, and let the consumer choose. The same API that lets a partner route into your Core lets your Core route back out.
Walk any model, step by step
Toggle between Direct Lender, Multi-Lender, and Hybrid to trace one application end to end. Same Core underneath; the difference is who funds and how it routes.
Software. Not a lender. Not a redirect portal.
OneApp Finance is licensed software you deploy and brand. You bring the capital and bear the credit risk; the platform is never the lender-of-record and never the consumer brand. It originates loans and stops at the servicer handoff. It does not hold the loan ledger, post payments, or do collections. And it stays neutral on the legal facts that vary by deployment: those are resolved by your counsel, and the build is designed to stay safely inert until they are.
Seven components, one Core
Each piece is built to stand alone and to work together. Start anywhere.
Config Studio
Stand up your program (products, rate cards, credit policy, vendors, brand) in no-code editors, with versioning, dual-control approvals, and a compliance floor you can tighten but never relax.
Explore →Operations Portal
The all-day console for your teams: queues, the deal cockpit, the dual-control funding console, and an override grammar that moves files forward without ever silently bypassing a floor.
Explore →Dealer Management
Onboard contractors through a real KYB gate, track good-standing on a six-state machine separate from onboarding, and re-check standing and certification at the moment of every draw.
Explore →Modularity & API
One public REST API and signed webhooks, the same contract our own screens use. Capability-based adapters mean swapping a vendor is config, not code.
Explore →Compliance
A frozen set of 16 non-negotiable rules, designed so the Core re-performs them (structural, not a setting) with a four-tier override model and an evidence-first design where every gate is satisfied by a real artifact, never a skipped checkbox.
Explore →Security
Single-tenant by design: your own cloud, your own database, your vendor contracts and keys. No god-mode, separation of duties, and an append-only audit trail.
Explore →Developers
The API reference: a public REST surface, OAuth2, signed webhooks, idempotency, and version-pinned decisions. The contract you build against.
Explore →Pick your path
Two ways operators run OneApp Finance. Same Core underneath.
For direct lenders
Run the full origination stack under your own brand: borrower flow, dealer tools, and ops console on one Core. The RUN configuration, end to end.
Explore →For multi-lender programs
Pre-qualify once, then route the application to a panel of lenders you choose and let the consumer choose from real offers. The fan-out and the inbound partner seam run on the same Core.
Explore →Your instance. Your data. Your isolation.
Every operator gets its own isolated install with its own database, single-tenant by deployment, not a shared table with a tenant column. The deployment is the hard isolation boundary, sold as a feature. Run it in your own cloud, or let OneApp Finance run it for you. Inside one instance, a program is a first-class scope, so one deployment can run home-improvement, solar, or several channel partners side by side, each with its own products, rates, workflows, and brand.
See the Core run, your way.
Walk the three modes on a live deployment and see where your stack fits.