Open Money Stack
Dashboard and backoffice for Polygon’s money-movement stack
After Sequence was acquired by Polygon Labs, I joined the small team building Open Money Stack — Polygon’s new vision for moving money across wallets, ramps, and chains from one product surface.
What it is
Open Money Stack is Polygon’s integrated money-movement platform: a single API and dashboard for deposits, stablecoin movement, wallets, payouts, keys, and team access. The dashboard is the operator control plane for that stack.
I was part of the first seven months of development, when the product was still being shaped rather than incrementally extended.
My work
I contributed across the design system, the OMS dashboard, and the backoffice applications — on both frontend and backend. The work sat at the boundary between product UX, internal tooling, and the services those surfaces depend on.
- Dashboard product surfaces for operating the stack.
- Backoffice applications used internally to run the product.
- Shared design-system components used across those apps.
- Frontend and backend work on the same product surfaces, not only UI.
Owning authentication
I owned authentication for the dashboard and related apps. That included SAML/OIDC SSO, Google SSO, passwordless login, invitation flows, and the ongoing work of keeping those paths reliable as the product evolved.
Auth ran on Frontegg. I stayed in direct contact with their team: reporting bugs, asking for product changes, and following issues through instead of treating the vendor as a black box.
Architecture
01
Operator signs in through the identity provider
02
SSO, passwordless, and invitation flows land in the dashboard
03
Team permissions and API keys are managed in-product
04
Backoffice apps operate wallets, ramps, and internal workflows
05
Shared design system keeps surfaces consistent
06
Backend services back the control plane
Engineering notes
Treat auth as a product surface
SSO, invitations, and passwordless login are not setup chores. They are the first operator experience and the permission boundary for everything else in the dashboard.
Stay close to the identity vendor
When authentication is outsourced, the integration still needs an owner. Filing bugs, requesting features, and keeping a working relationship with the vendor team was part of shipping the product, not support overhead.
Share one design system across dashboard and backoffice
Operator and internal tools should feel like the same product. Reusable components made it possible to move faster without letting each app invent its own UI language.