> For the complete documentation index, see [llms.txt](https://docs.nofi.money/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nofi.money/how-we-fix-it/tech-stack.md).

# Tech Stack

{% hint style="info" %}
**Philosophy:** Use best-in-class infrastructure for each piece of the stack rather than rebuilding what others have already solved well. Build once, deploy many through white-labeling.
{% endhint %}

NØFI is built on a small set of specialized infrastructure partners rather than a single vertically-integrated stack. This lets the team focus on **distribution and product** rather than re-solving solved problems — and enables white-label deployments to launch on the same proven infrastructure with minimal additional engineering.

## Infrastructure Partners

| Partner                                 | Role                                              | Status             |
| --------------------------------------- | ------------------------------------------------- | ------------------ |
| [**Privy**](https://privy.io)           | Embedded self-custodial wallets — no seed phrases | ✅ Live             |
| [**Gnosis Pay**](https://gnosispay.com) | Self-custodial Visa card                          | ✅ Live in Colombia |
| [**Koywe**](https://koywe.com)          | COP off-ramps — local currency conversion         | ✅ Live             |
| [**Bridge**](https://bridge.xyz)        | USD rails and stablecoin infrastructure           | ✅ Live             |
| [**M^0**](https://m0.org)               | Pass-through yield on idle stablecoin balances    | ✅ Live             |
| [**LI.FI**](https://li.fi)              | Cross-chain routing and liquidity aggregation     | ✅ Live             |

## White-Label Architecture

The same infrastructure powers every deployment:

* **Shared core:** Wallet creation, card issuance, off-ramps, yield, and routing are handled once
* **Brand layer:** Each white-label gets its own app, branding, onboarding flow, and community-specific features
* **Local partners:** Off-ramp and compliance partners are added per-market (Koywe for Colombia, additional partners for SEA)

### How a White-Label Settlement Works

Using DaywaPay (Thailand → Myanmar corridor) as an example:

```
Local Currency In (THB)  →  NØFI Engine Settles  →  Local Currency Out (MMK)
     User sends THB      →   Converts via stablecoins   →   Recipient receives MMK via local bank
```

The brand is the surface — what users see and trust. NØFI is the engine underneath — handling conversion, settlement, and compliance. This separation means new corridors launch without rebuilding infrastructure.

> **Build vs. buy decision:** Every month spent rebuilding wallet, card, off-ramp, or yield infrastructure in-house is a month not spent acquiring and serving users. In a market where distribution is the moat, speed to market matters more than vertical integration.

As volume scales across all brands, NØFI negotiates enterprise-tier pricing and custom routing with each partner — the economics improve with combined scale.

{% hint style="success" %}
**Result:** NØFI shipped a live product with self-custodial wallet, Visa card, off-ramps, yield, and cross-chain routing — using a team of under 10 people. The same stack powers white-label deployments with minimal additional engineering.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.nofi.money/how-we-fix-it/tech-stack.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.