Fedi company primary sources — 2026-08-09

Project status in this pass

• Existing projects/fedi note was useful on the consumer shell, but it still flattened too much of the distribution and setup authority into the product note.
• This pass split out ../companies/fedi.md so the operator boundary around Mini App review, wallet-service setup, regional support, and the legal shell stops hiding inside the app summary.

Primary-source snapshots

1) Main site and company page

• URLs:
  • https://www.fedi.xyz/
  • https://www.fedi.xyz/company
• Key excerpt:
  • The homepage presents Fedi as a privacy-first Bitcoin app combining wallet, chat, community spaces, and Mini Apps.
  • The company page says 100+ communities are registered to roll out Fedi and 50+ Mini Apps are available.
  • The site repeatedly markets wallet services powered by Fedimint and frames Fedi as the human-and-technology packaging layer around those services.
• Why it matters:
  • This is strong evidence that Fedi is selling a company-run distribution and onboarding shell, not just publishing a neutral protocol client.

2) Builders page and Mini App review flow

• URL: https://www.fedi.xyz/fedi-for-builders
• Key excerpt:
  • The builders page says Fedi is open source and invites developers to build Mini Apps and private Bitcoin ecash applications.
  • It tells builders to submit Mini Apps for review in order to get featured in the public catalog.
• Why it matters:
  • Featured distribution is company-mediated. Even in an open ecosystem, Fedi still controls a meaningful application-admission and promotion surface.

3) Wallet-service creation page

• URL: https://www.fedi.xyz/create-a-wallet-service
• Key excerpt:
  • The page presents several launch paths for a Fedimint-powered wallet service, including G-Bot setup, Start9, Umbrel, Nodana, and DIY deployment.
  • It explicitly offers team follow-up for people who need help setting up a federation.
• Why it matters:
  • Fedi is not only documenting Fedimint; it is trying to stay in the practical onboarding path for communities that want to launch wallet services.

4) G-Bot wallet-service setup page

• URL: https://www.fedi.xyz/gbot-wallet-service-setup
• Key excerpt:
  • The page says users can create a wallet service in minutes through G-Bot.
  • It advertises paid setup plans and gives named regional contacts / Fedi Masters.
  • It also says communities can personalize federations and now charge federation fees inside the setup flow.
• Why it matters:
  • This is unusually explicit evidence that Fedi the company is operating a setup, pricing, and support surface around federation creation rather than only pointing to open-source software.

5) Privacy policy and terms of use

• URLs:
  • https://www.fedi.xyz/privacy-policy
  • https://www.fedi.xyz/terms-of-use
• Key excerpt:
  • Both documents identify the operator as Fedi, Inc..
  • The privacy policy says Fedi, Inc. processes personal information in connection with the website and app.
  • The terms say Fedi may restrict access to the website and govern use of hosted services.
• Why it matters:
  • The legal and data-handling perimeter is company-shaped even when the product rhetoric emphasizes privacy and community custody.

6) Public monorepo README

• URL: https://raw.githubusercontent.com/fedixyz/fedi/master/README.md
• Key excerpt:
  • The README says the repository contains the full Fedi tech stack, including the Rust core, custom Fedimint modules, Matrix chat, communities, and the apps that ship to users.
• Why it matters:
  • This shows Fedi is not merely a skin over Fedimint. The company is maintaining a broad packaged stack with its own modules and application-layer operating assumptions.

Working conclusion

Fedi is more useful as two layers. projects/fedi should stay on the consumer app surface: wallet, chat, Mini Apps, and the user-facing Fedimint shell. companies/fedi should capture the named operator boundary where release workflow, Mini App review, setup assistance, support, pricing, and legal/data policy actually sit.