Wyre
Became Wyre →
Wyre is our open-source expense and payroll system for paying employees, contractors and vendors from one place: spend infrastructure, MIT licensed under Tecmie Corporation. We built it for businesses running payroll across borders, with African SMBs in mind: teams that need fiat, crypto and mobile-money rails side by side rather than one bank transfer option.
We created the repo in September 2022 inside the Daccred organisation, splitting it out of the credentials monorepo. Real work ran from January to April 2023, and we never took the “early alpha” label off. The payment-links idea carried on as the Wyre entry in the portfolio.
What it does
Payroll without geographic limits, payment in any currency including crypto, reimbursement requests, contractor payment requests with auto-generated invoices, and unique payment links.
There was a much longer list on the roadmap: signup and invites, payroll approval and scheduling, a transactions view, compensation edits, pension, health insurance, tax withholding, salary advances. Treat that as roadmap. It is not what we shipped.
We recorded three Looms while it was working: a product overview, an integrations overview, and a walkthrough of employee payslips and payout methods. They are in the resources, and they show the UI better than we can describe it here.
How we built it
Next.js, tRPC, Prisma, Neon serverless Postgres, Redis, Chakra UI, Twilio and SendGrid, arranged as a Lerna and Yarn workspaces monorepo. Two apps, apps/web for admins and apps/employee for staff, plus shared api, db, dialog and env packages.
We planned the payment layer in four groups: open banking through Mono, Stitch, Anchor and OnePipe; fiat rails through Paystack, ExpressPayGH and Flutterwave; crypto rails through Fluidcoins, Lazerpay and Coinprofile; and mobile money through MTN MoMo and M-Pesa. Most of those stayed plans.
It is all open: daccred/wyre is public under MIT, 380 commits from 8 contributors.
Every great product starts with someone who refuses to accept what exists today.
If that's you, we should
talk about your future product