NOAvailable

Northframe

The operations layer for teams who still run the night shift.

From $890 per month

MEBeta

Meridian

Client workspaces and living billing for project-shaped firms.

From $190 per month

NewFree apps from the studio. Get yours

Independent product studio

Webuildproductsthatsolverealproblems.

We design, engineer, and ship software for developers, operators, and modern digital teams. The catalog is the long-term asset: payment infrastructure, operations software, and engagement systems we actually run with clients. Selected builds exist to fund and inform that catalog — not to turn the studio into a generic agency.

Explore ProductsWork With Us

A product studio for teams who still have to operate what they buy — treasuries, night desks, and project firms included.

01CatalogUse StablePaySelf-hosted payment gateway software. You deploy it. We do not process payments as a service.02EngineeringCommission a buildProduct development, frontend, Web3, or internal tools — only when the scope can ship.
Practice
Since 2019Independent studio. Products first, selected builds second.
In production
28 systemsCatalog products and commissioned software still being operated.
Catalog
3 productsStablePay, Northframe, and Meridian — each with a public job.
First release
6-week medianA focused cut in a real environment, then a second cut from use.

Built with a stack you can inspect

React
Next.js
TypeScript
Tailwind CSS
Radix UI
Framer
Node.js
NestJS
PostgreSQL
Redis
Docker
GraphQL
Prisma
Ethereum
Solana
Solidity
Polygon
Chainlink
Ethers.js
WalletConnect
React
Next.js
TypeScript
Tailwind CSS
Radix UI
Framer
Node.js
NestJS
PostgreSQL
Redis
Docker
GraphQL
Prisma
Ethereum
Solana
Solidity
Polygon
Chainlink
Ethers.js
WalletConnect
React
Next.js
TypeScript
Tailwind CSS
Radix UI
Framer
Node.js
NestJS
PostgreSQL
Redis
Docker
GraphQL
Prisma
Ethereum
Solana
Solidity
Polygon
Chainlink
Ethers.js
WalletConnect
React
Next.js
TypeScript
Tailwind CSS
Radix UI
Framer
Node.js
NestJS
PostgreSQL
Redis
Docker
GraphQL
Prisma
Ethereum
Solana
Solidity
Polygon
Chainlink
Ethers.js
WalletConnect
Currently shipping

Products we've built.

Three products, each with a job, a status, and a commercial path. StablePay for teams who want to own payment infrastructure. Northframe for operations that still run after dark. Meridian for firms whose work is project-shaped.

Infrastructure · Early Access

StablePay

Self-hosted stablecoin payment infrastructure.

StablePay is payment gateway software — not a hosted processor. Customers purchase the software, deploy it on infrastructure they operate, and integrate it into their own applications. The studio does not hold customer funds, run customer wallets, or act as a bank. Production signing, RPC providers, databases, and secrets stay under the customer's control.

TypeScriptREST APIDockerPostgreSQLWebhooks
Explore StablePay

Who it is for

  • Developers integrating stablecoin payments without building a full gateway
  • Businesses that want to own payment infrastructure instead of renting it
  • Agencies deploying a branded gateway for clients they already operate

What it is

  • Self-hosted deployment on customer infrastructure
  • Payment intents, payment links, and invoices through a versioned API
  • Stablecoin-native flows with configurable tokens and networks
  • Signed webhooks as payments move through their lifecycle
  • Operational dashboard for tracking, confirmation, and settlement status

What it is not

  • Not a hosted payment processor
  • Not a custodian or bank
  • Does not hold customer funds as a service
  • Does not provide legal or compliance services
NO
Available

Northframe

The operations layer for teams who still run the night shift.

From $890 per month

Business SoftwareNext.jsTypeScriptPostgreSQL
Explore Product
ME
Beta

Meridian

Client workspaces and living billing for project-shaped firms.

From $190 per month

SaaSNext.jsTypeScriptPostgreSQL
Explore Product

StablePay remains self-hosted software: you purchase it, deploy it, and keep signing and funds in your environment. Northframe and Meridian follow the same rule — products you operate, not platforms we quietly run for you.

Free downloads

Free apps, on the house.

Small, useful software we built and are giving away. Enter your email, get a private download link. Free for personal use.

FreeDeveloper toolPersonal use

ContractLens

A self-hosted Solidity risk scanner that runs entirely on your machine.

10
AST-based security rules
32
scanner tests, all passing
0 bytes
of your source ever uploaded
3
ways in: web app, CLI, library
Explore & get it freev1.0.0 · 244 KB · macOS · Windows · Linux
ContractLens · scan result
67
of 100

Automated Risk Score

Critical0
High2
Medium1
Low2
Info0
5 findings6 functions · 53 ms
See all free apps
  1. 01

    We ship products you operate — keys, data, and on-call stay with you.

  2. 02

    Every public story is a named engagement with a written handover.

  3. 03

    No custody, no legal shop, no transformation programme in search of a problem.

Origin

Built from the systems people still operate by hand.

The studio began when a payments rebuild refused to fit a hosted processor. The team that owned the risk wanted software they could deploy, inspect, and hand to the next engineer. That engagement became StablePay. The next few years kept rhyming: freight exceptions living in a workbook, a creative studio invoicing from inboxes, a field company paying contractors through a vendor they could not explain. We kept the same shape — a product you can run, and a build only when the problem is written down.

  1. 2019

    Studio opens

    Independent practice. First commissioned products for operators who were tired of rented platforms.

  2. 2021

    StablePay takes shape

    A self-hosted gateway, sold as software. The catalog stops being a slide and becomes a deploy.

  3. 2023

    Northframe ships

    Halcyon's night desk becomes the first public proof that operations software can respect the after-hours shift.

  4. 2025

    Meridian enters beta

    Project-shaped firms get a workspace and a billing surface that can survive a change order.

Work

Selected work.

Selected engagements from treasury, freight, creative studios, and field operations. Each study is a named team, a written problem, and a system they still run.

A marketplace treasury that could run at 2am

Vellum needed stablecoin settlement they could operate themselves — not another hosted processor with a black-box ledger.

17 days · Time to first live payment

Vellum MarketsDigital assets2024
Read the study

Dispatch without the spreadsheet stack

A regional freight operator replaced four shared workbooks with an exception-first operations layer their night shift could actually use.

Retired · Workbook usage after 30 days

Halcyon FreightLogistics2023
Read the study

A studio that stopped billing from inboxes

A forty-person studio needed client workspaces, entitlements, and invoices that matched how productions actually run — not how SaaS billing assumes they run.

−38% · Invoice cycle time

Aperture CollectiveCreative services2024
Read the study
All selected work
Voices

What operators say after the handover.

These are people who still run the systems. We ask for a sentence they would repeat to a peer — not a slogan for a landing page.

We stopped renting a processor and started running a system we could explain to our own engineers. That change is the difference between a payments feature and a treasury operation.
Mira AdelHead of Treasury, Vellum Markets
The first week after go-live, dispatch stopped asking finance for a spreadsheet. That is the only metric I still quote in the board pack.
Jonas RheeChief Operating Officer, Halcyon Freight
They treated billing as a product surface, not an afterthought. Our producers finally have a place that matches how the work actually happens.
Elena VossManaging Partner, Aperture Collective
Contractor settlement used to be a weekend job. It is now a weekday workflow with an audit trail the auditors actually like.
Samuel OkoyeVP of Field Operations, Helios Grid
Studio

Small studio. Serious software.

We sit between a product company and a software studio. The work started with payment infrastructure nobody wanted to rent, then widened to the systems that sit around money: exceptions, approvals, client workspaces, and the records people still keep in a spreadsheet at 2am.

Product-first means the catalog comes before the services page. Engineering-led means interfaces, APIs, deployment, and operations are designed as one system. Client work is how the catalog stays honest — Vellum's treasury, Halcyon's night desk, Aperture's change orders. We would rather own a focused catalog and take on the engineering required to keep it real.

Boundaries
  • Generic agency retainers with no product outcome
  • Staff-augmentation benches disguised as a studio
  • Hosting or custodial services presented as if they were the product
  • Legal, tax, or compliance advice
  • Unbounded 'digital transformation' programmes
Who it's for

Three ways in.

The studio is small. These pages exist so you can skip the generic pitch and read the path that matches your situation — then decide whether a product or a build is the honest next step.

Businesses

Internal tools, SaaS, and operational software around how work already happens.

Approvals, inventory, billing-adjacent flows, reporting, and the integrations between tools — when someone will operate the result.

Internal toolsSaaSOperationsIntegrations
Read this path

Developers

APIs, self-hosted products, and infrastructure you can inspect and run yourself.

Versioned APIs, signed webhooks, Docker-based deploys, and docs that describe the actual system.

APIsSelf-hostedWebhooksDocs
Read this path

Startups & agencies

A first production version when you do not have a full engineering team yet.

A complete first version with a written scope — not a staff-augmentation bench.

MVPProduct engineeringFrontendPartnership
Read this path
Process

How a piece of software actually gets built.

The sequence is deliberately short. We would rather complete a focused system than run a theatre of workshops. You bring the use case, the constraints, and who has to operate the result.

  1. 01

    Frame the problem

    We start with the use case, the constraints, and who the software has to serve. Features come after the problem is clear.

    A written problem, operator, and non-goals — not a feature dump.

  2. 02

    Design the smallest complete product

    A focused scope that can ship. Interfaces, data model, and operational shape are designed together — not as afterthoughts.

    A bounded scope: screens, data, and how the system is run.

  3. 03

    Engineer for production

    Architecture, authentication, deployment, observability, and documentation are part of the build, not a later phase.

    Software that can be deployed, observed, and handed over.

  4. 04

    Ship, then iterate

    We prefer a working system in a real environment over a long sequence of demos. Feedback from use drives the next cut.

    A release in the environment that matters, then a next cut from use.

Services

Need something built for your business?.

Selected teams only. Product development, frontend engineering, Web3 integrations, custom operational software, and technical consultation. Products still come first — a services engagement has to produce software that can be operated.

Product Development

Turn an idea into a production-ready digital product.

A scoped product with a clear purpose

Read this service

Frontend Engineering

Build modern React and Next.js applications with maintainable architecture.

Component systems that stay consistent

Read this service

Web3 Development

Build blockchain-enabled applications and integrations.

Wallet and network integration where needed

Read this service

Custom Software

Build internal tools and business systems around your actual workflow.

Tools mapped to real processes

Read this service

Technical Consultation

Independent technical advice on architecture, payments, build-versus-buy, and scope — delivered in writing.

A written recommendation with the reasoning behind it

Read this service
All services
Journal

Writing from the work.

Essays and engineering notes we would send a serious buyer before the first message. Not a content calendar.

30 essays and guides8 guide11 engineering5 tips6 journal

Browse all writing
Latest · Guide16 Sep 2026

What agencies should know before adding payments to a client project

Clients ask for 'a payments option' as if it were a plugin. It is a long-lived responsibility. Here is how to scope it without becoming a payments company.

StablePayAgenciesClient work
Omar Farouk5 min read
Engineering10 Sep 2026

Designing adapters that do not try to own your ERP

Operations software earns trust by sitting between systems, not replacing them. The adapter layer is where that promise is kept or broken.

Daniel Whitfield7 min
Guide2 Sep 2026

Paying contractors in stablecoin: an operational playbook

Faster settlement is easy to promise. The hard part is approvals, records, and an ERP that still has to balance. Here is how a field-services company did it.

Omar Farouk6 min
FAQ

Straight answers.

Is this a product company or an agency?

A product-focused digital studio. The catalog is the primary long-term asset. Services are a secondary channel for selected engagements — not the whole brand.

Do you only build Web3 products?

No. We work across SaaS, developer tools, business software, and Web3 where the problem actually requires it.

Can we hire you for a custom project?

Yes, for selected teams. Write what you are building, what you need help with, and any hard constraints. We respond when it is a good fit.

Do you offer technical consultation?

Yes. We advise selected teams on architecture, payments and Web3 integration, build-versus-buy decisions, security readiness, and scoping — as written Q&A, asynchronous reviews, and decision briefs that end in a written recommendation. We work entirely in writing over the text channel you choose — no calls — and agree scope and fee in writing first.

Where do product pricing and docs live?

With each product. Studio pages introduce the software and its status. Pricing, licenses, and documentation belong to the product experience as they are published.

Is StablePay a hosted payment processor?

No. StablePay is self-hosted software. You deploy and operate it. The studio does not hold customer funds or run customer wallets as a service.

Can we read client work before we talk?

Yes. Start with Vellum Markets, Halcyon Freight, and Aperture Collective on the Work page. Each study names the team, the problem, the stack, and what changed after handover.

Do you provide hosting, legal, or compliance services?

Not as part of the standard studio offering. Customers are responsible for infrastructure, legal, tax, and regulatory requirements in their own jurisdiction.

Have something worth building?

Whether you want a product from the catalog or a team to help ship one, start with a short, specific note: the problem, the constraints, and what has to exist in production.

Explore ProductsWork With Us

Free apps from the studio. Enter your email, get a private download link. Free for personal use.

Get them free

Have a product to sell? We review, list, and sell it for you — you keep 90% of every sale.

Apply to sell with us