Skip to content
@mbotyha

Mbotyha

Ára Pe'aha Aĩ

One key. Your money, your knowledge, your AI.

Self-custodial payment and AI tools for businesses in emerging markets, starting in Paraguay.

The same rule drives both: whoever holds the key holds the asset. In payments, the seed holds the funds. In AI, the company's knowledge stays in its own git repo, and model vendors are meant to see one isolated task at a time, never the whole.


Two stacks, two servers

Each stack runs in Docker on its own VPS. Both can be self-hosted.

Stack What it does Repos
PAY Multi-rail inbound payments (Bitcoin, stablecoins, P2P and fiat rails) with self-custodial settlement, on top of BTCPay Server /pay (MIT)
AI Company memory as Markdown in git, a knowledge graph of it (testing), and a CPU router (planned) that sends each task to commercial or self-hosted models with only the context that task needs /os (MIT engine) + content (private memory)

Architecture, rails, and roadmap for PAY: pay README. The AI model, markers, and router: os README.


Principles

  • Self-custodial by default: funds and knowledge never sit with a platform
  • Agnostic in practice: the usable rail or model matters more than ideology
  • Modular: rails, services, and models can be enabled or left out per use case
  • Open source: public components are MIT; a paid closed-source offering funds their long-term maintenance
  • Dogfooded: the company building this runs on it every day

Community & Contact

Pinned Loading

  1. pay pay Public

    Orchestrator monorepo. It assembles payment rails, business flows, and support services into a single Nuxt-based workspace.

    JavaScript

  2. ai ai Public

    Python

Repositories

Showing 6 of 6 repositories

Top languages

Loading…

Most used topics

Loading…