Back to 0fee
0fee

The Numbers: 86 Sessions, 70,000+ Lines of Code

The complete statistical breakdown of 0fee.dev: 86 sessions, 70,000+ lines, 90+ endpoints, 8 SDKs, and more. By Juste A. Gnimavo.

Thales & Claude | March 25, 2026 8 min 0fee
statisticsmetricscode-analysisbuild-summary

Numbers tell the story that narratives cannot. How big is 0fee.dev? How much code did 86 sessions produce? How many endpoints, how many providers, how many countries? This article is the complete statistical breakdown of the 0fee.dev codebase as of Session 086.

The Headline Numbers

MetricValue
Total sessions86
Calendar days80 (Dec 10, 2025 -- Feb 28, 2026)
Lines of code~70,000+
Human engineers0
AI CTOClaude (Anthropic)
CEOJuste A. GNIMAVO
LocationAbidjan, Ivory Coast

Development Metrics

MetricValue
Sessions per day (average)1.075
Most sessions in one day13 (December 12, 2025)
Days with zero sessions~8
Average session duration~45 minutes (estimated)
Longest session~90 minutes
Shortest session~15 minutes

Backend Statistics

ComponentCount
API endpoints90+
SQLAlchemy ORM models39
Database tables39
Provider adapters8 (Stripe, PayPal, Hub2, PawaPay, BUI, PaiementPro, CinetPay, Test)
Supported providers (including sub-providers)53+
Payment methods117
Countries covered200+
Backend languages (i18n)15
Middleware components6 (auth, rate limit, CORS, i18n, logging, idempotency)
Celery background tasks8
API documentation pages90+

API Endpoint Breakdown

CategoryEndpoints
Authentication (login, OAuth, refresh)12
Applications (CRUD, config)8
Payments (create, status, cancel)6
Transactions (list, detail, export)5
Providers (list, detail, methods)4
Payment Methods (list, filter)3
Webhooks (CRUD, deliveries)7
Invoices (list, detail, PDF)5
Payment Links (CRUD)5
Billing (balance, cycle, add funds)4
Feature Requests (CRUD, vote, comment)20
Admin (users, apps, transactions, stats)8
Health/Status2
i18n1
Total90+

Frontend Statistics

ComponentCount
Dashboard pages19
Frontend languages (i18n)5 (English, French, Spanish, Portuguese, Arabic)
Checkout widget size~21KB (IIFE, minified)
Theme supportDark + Light (localStorage persisted)
Responsive breakpoints3 (mobile, tablet, desktop)

Dashboard Pages

  1. Dashboard (overview)
  2. Applications (list)
  3. Application Detail
  4. Application Settings
  5. Transactions (list)
  6. Transaction Detail
  7. Providers
  8. Payment Methods
  9. Webhooks
  10. Analytics
  11. Invoices
  12. Invoice Detail
  13. Payment Links
  14. Wallet / Add Funds
  15. Settings / Profile
  16. API Keys
  17. Get Started (onboarding stepper)
  18. Developer Console
  19. Feature Requests

SDK Statistics

SDKLanguageVersionDependenciesSize
@0fee/nodeTypeScriptv3.00~15KB
zerofee-pythonPythonv3.0httpx~12KB
zerofee-goGov3.00~18KB
zerofee-phpPHPv3.00~14KB
zerofee-javaJavav3.00~20KB
zerofee-rustRustv3.0reqwest, serde~16KB
@0fee/flutterDartv3.0http~11KB
@0fee/react-nativeTypeScriptv3.00 (wraps @0fee/node)~8KB

Total SDKs: 8 in 7 programming languages

API coverage: 79% of public endpoints

Platform Plugins

PluginPlatformVersion
0fee for WHMCSWHMCSv1.0
0fee for WordPressWordPressv1.0
0fee for WooCommerceWooCommercev1.0

Total plugins: 3

Database Statistics (as of Session 086)

MetricValue
Tables39
Total rows migrated to PostgreSQL1,204
Largest table (rows)payment_events
Largest table (columns)transactions (18 columns)
Foreign key relationships47
Unique constraints12
JSON columns8

Tables by Category

CategoryTablesRows
Core (users, apps, keys)4~92
Payments (transactions, events, links)5~799
Providers (providers, methods, config)4~170
Webhooks (hooks, deliveries, events)3~53
Billing (cycles, fees, coupons, wallet)6~45
Auth (OAuth states, sessions, tokens)3~15
Admin (audit logs, actions)2~12
Features (requests, votes, comments, subs)4~8
i18n (translations, languages)2~10
Config (currencies, countries, methods, branding)4~0 (populated at runtime)
Other (SDK downloads, AI conversations)2~0
Total39~1,204

Infrastructure Statistics

ComponentSpecification
Docker services3 (frontend, backend, worker)
Frontend image size~40MB (nginx + static files)
Backend image size~350MB (Python + dependencies)
Worker image size~350MB (Python + Celery)
DatabasePostgreSQL 17
Cache/BrokerRedis
Deployment platformEasyPanel
SSLLet's Encrypt (auto-renewal)
Domains0fee.dev, api.0fee.dev

Code Volume Estimates

Precise line counts are approximate because they depend on what you count (comments, blank lines, generated files):

ComponentEstimated Lines
Backend (Python)~25,000
Frontend (SolidJS/TypeScript)~18,000
SDKs (all 8)~12,000
Checkout widget~3,000
Marketing website~4,000
Docker/config/migrations~2,000
Platform plugins~3,000
Documentation~3,000
Total~70,000+

Provider Coverage

ProviderCountriesMethodsType
Stripe46+Cards, wallets, bank transfersGlobal
PayPal200+PayPal balance, cardsGlobal
Hub28Mobile money, cardsFrancophone Africa
PawaPay21+Mobile moneyPan-African
BUI5Cards, mobile moneyWest Africa
PaiementPro3Mobile money, cardsWest Africa
CinetPay15+Mobile money, cardsAfrica
TestAllAllDevelopment

Total unique providers (including sub-providers): 53+

Total payment methods across all providers: 117

Country coverage: 200+

Session Distribution by Type

Session TypeCountPercentage
Feature development3541%
Bug fixing / debugging2023%
UI/UX polish1012%
Infrastructure / DevOps89%
SDK development67%
Security / compliance45%
Documentation33%
Total86100%

The 41/23 split between feature development and bug fixing is notable. For every two sessions spent building, approximately one session was spent fixing. This is a common ratio in fast-paced development and suggests that the speed of development did not come at an extreme quality cost -- though it was not quality-free either.

Comparative Context

To put these numbers in perspective:

Metric0fee.devTypical Startup (5-person team)
Time to MVP2 days3-6 months
Time to production80 days12-18 months
Engineers0 (AI only)3-5
SDKs at launch81-2
Provider integrations53+2-3
Monthly engineering cost$0 (API costs only)$50,000-$150,000

These comparisons come with caveats. A 5-person team builds institutional knowledge, handles customer support, writes tests, maintains CI/CD, and conducts code reviews. The 0fee.dev model trades all of that for speed. The comparison is not "better" or "worse" -- it is a fundamentally different approach with different trade-offs.

What the Numbers Do Not Show

The numbers do not capture:

  • Decision quality. How many of the 86 sessions produced code that needed to be rewritten later? (At least 15, based on the session logs.)
  • Test coverage. Currently at 0%. No automated tests exist. This is a known gap.
  • Customer feedback. The platform was built before any customer used it. Real-world usage will reveal issues that development never surfaced.
  • Maintenance burden. 70,000+ lines of code need ongoing maintenance. With zero human engineers, every maintenance session competes with feature development.

The numbers tell the story of what was built. The next chapter -- how it performs in production with real users and real money -- is still being written.


This article is part of the "How We Built 0fee.dev" series. 0fee.dev is a payment orchestrator covering 53+ providers across 200+ countries, built by Juste A. GNIMAVO and Claude from Abidjan with zero human engineers. Follow the series for the complete build story.

Share this article:

Responses

Write a response
0/2000
Loading responses...

Related Articles