Architecture
The engine that tracks your gig earnings across every app, auto-logs IRS mileage, and keeps you ahead of quarterly taxes.
UnifyOne's architecture is the Cathedral Framework: an earnings data foundation built in sequence under GigIQ, Tax Autopilot, Money Manager, and Kai — where each pillar is load-bearing and completed before the next is raised, so the numbers you file quarterly taxes on are accurate end to end.
Sequential Construction.
Permanent Foundation.
Medieval cathedral builders did not decorate before the foundation was sealed. They did not install stained glass before the vault was load-tested. They built in sequence — crypt, nave, transept, clerestory, spire — because each layer depended on the structural integrity of the one below it.
UnifyOne is built on the same principle. Earnings capture before mileage and tax math. Tax math before budgeting. Budgeting before AI. Each pillar is a load-bearing wall, not a decorative facade — because your IRS deduction total and your Form 1040-ES figures are only as trustworthy as the layer beneath them.
The result is a platform where the numbers a gig worker files quarterly taxes on are accurate end to end — no stale figures, no manual reconciliation at tax time, no compounding errors that surface in April.
The Pillars
Earnings Data Foundation
Your earnings across DoorDash, Uber, Lyft, Instacart, Amazon Flex, Grubhub, Shipt, Upwork, Fiverr and more, captured in one isolated vault. Each worker's data is structurally separated at the schema level — not by convention, not by middleware. Every shift, payout, and mile is a load-bearing record the layers above depend on.
GigIQ
Reads your real earnings data to show which hours and zones actually pay the most after fuel and expenses. Specific scheduling recommendations drawn from what every shift nets you — not industry benchmarks, not generic advice. The intelligence layer reads the same schema as the foundation, so the numbers are never stale.
Tax Autopilot
Auto-captures mileage from every logged shift at the IRS standard rate and keeps a real-time year-to-date deduction total. Quarterly estimated-tax alerts surface the Form 1040-ES figures you need before each deadline — built on your real after-expense income, so April is never a surprise.
Money Manager
Budgeting, goals, and spending analysis built on your real after-expense gig income — so your plan matches what you actually take home, not a salaried estimate. Reads the same earnings and deduction records as Tax Autopilot, with no separate data entry.
Kai
A context-aware sidekick for tax, route, and scheduling questions answered on your own numbers — your shift earnings and mileage logs, not generic tips. The AI reads your data server-side and returns specific answers. AI tools are included when they ship.
Full Stack
Architecture Questions
What is the Cathedral Framework?
The Cathedral Framework is UnifyOne's architectural philosophy: build the platform sequentially, with each layer load-bearing before the next is raised. Earnings capture comes before mileage and tax math, tax math before budgeting, and all of it before AI. Every pillar is structural, not a decorative add-on — so the numbers a gig worker relies on for quarterly taxes are accurate end to end.
What are the four structural pillars of UnifyOne?
The four pillars are GigIQ (shift and earnings intelligence across DoorDash, Uber, Lyft, Instacart, Amazon Flex, Grubhub, Shipt, Upwork, Fiverr and more), Tax Autopilot (IRS mileage logging at the standard rate plus quarterly estimated taxes and Form 1040-ES figures), Money Manager (budgeting and goals built on real after-expense income), and Kai (a context-aware AI sidekick for tax, route, and scheduling questions). They rest on an earnings data foundation that every pillar reads from.
How does UnifyOne keep each worker's earnings and tax data private?
Every worker's account is an isolated vault. Earnings, mileage, deductions, and tax figures are separated at the schema level and enforced with JWT sessions and role-based access control through Drizzle ORM on PostgreSQL — not by convention or middleware alone.
What technology stack is UnifyOne built on?
The frontend uses React 19, Vite, Tailwind CSS 4, and shadcn/ui. The API layer is tRPC 11 with Zod validation on Express. Earnings, mileage, and tax data live in PostgreSQL (Neon) via Drizzle ORM, with Supabase for credit metering and live updates. The platform ships on Node.js 22 with GitHub Actions CI.
Why build the earnings foundation before the tax and AI layers?
Because mileage logging, quarterly estimated taxes, and Kai's insights all read from your earnings data. If shift and earnings capture is not accurate and reliable first, every downstream number — your IRS deduction total, your Form 1040-ES figures, your budget — inherits that fragility. UnifyOne seals each load-bearing layer before adding the one above it, so tax time is never built on a shaky foundation.
The Foundation Is Ready.
Your Earnings Await.
Start free — shift tracker, mileage log, and tax tools, no card required. Upgrade to Pro at $4.99/mo when you want more.