LIVE
IDLEAwaiting updates…

Condensed Statement of Operations

Unaudited monthly P&L view for the LeXCorp portfolio, with the current operating snapshot compared against the disclosed future cost scenario.

LeXCorp Portfolio

Condensed Statement of Operations

Unaudited, USD in whole dollars, monthly cadence
As of 2026-04-26
Public-company-style profit and loss statement comparing current monthly actuals with a future cost scenario.
Line itemCurrent MonthlyFuture Scenario
Revenue$0$0
Monthly recurring revenue$0$0
Total revenue$0$0
Operating expenses$0$0
Bismarck v0.4 AWS backendaws$0$0
Bismarck v5 active backend baselineaws$0$850
Domain renewalsdomains$0$0
Metternich Cloudflare backendcloudflare$0$750
Neon shared databasedatabase$20$20
Poketo Azure agent backendazure$0$250
Vercel Hobby hostinghosting$0$0
Total operating expenses$20$1,870
Operating income (loss)($20)($1,870)
Net income (loss)($20)($1,870)

Notes to Statement

Current burn includes shared Neon only; the Bismarck v0.4 AWS backend was torn down on 2026-04-23 and the domain was retained for v5. The number in parentheses is a future monthly scenario if Bismarck v5 runs an active backend baseline and inactive Azure/Cloudflare backends are turned on. Domains are excluded until annual renewal totals are verified.

Basis of presentation

  • Vercel-hosted products remain on the Hobby plan at $0/month until upgraded.
  • Neon is one shared portfolio bill across apps, currently about $20/month including minor compute.
  • Bismarck v0.4 AWS infrastructure was torn down on 2026-04-23; v5 is a local rebuild until backend hosting is provisioned.
  • Poketo Azure and Metternich Cloudflare backends are present in code but treated as inactive future burn until activated.
  • Domain renewals are annual and should be amortized monthly once registrar totals are known.

Excluded from current statement

  • Annual domain renewals until registrar totals are provided.
  • Usage-based AI API calls until production usage is measured.
  • Stripe processing fees because they scale with revenue rather than fixed burn.
  • Bismarck v0.4 AWS infrastructure after 2026-04-23 teardown.
  • Experimental cloud infrastructure not mapped to active portfolio products.