DEV Community

Anton John Intes
Anton John Intes

Posted on

Building an Autonomous Compute Brokerage Engine with FastAPI and Supabase

Managing multi-provider compute allocations manually introduces unnecessary operational friction when scaling AI workloads, LLM inference, and automated backend execution.

To streamline this process, I built and brought live ApexSovereign.aiβ€”an autonomous compute brokerage engine designed to unify compute metering, double-entry financial ledgering, and sub-second API routing under a single system.


Technical Architecture & Stack

Here is how the platform is architected to operate with zero fixed infrastructure overhead:

  1. FastAPI (Python 3): Serves as our primary backend web service deployed on Render. Route handlers run via modularized startup entrypoints to maintain strict uptime execution and prevent module loading errors.
  2. Supabase PostgreSQL: Handles double-entry financial accounting via custom ledger_entries tables alongside structured system audit logs (audit_events).
  3. Live Financial Settlement: Integrated direct PayPal Business settlement rails, allowing real-time compute credit purchasing and instant ledger logging.
  4. Edge Routing: Vercel frontend proxy handling client-side requests and proxying traffic seamlessly to our backend engine.

Public Health & Diagnostic Verification

To ensure platform availability, we exposed a public health matrix endpoint that validates active database bindings and gateway connections on every poll:


Pilot Application Program

Our Pilot Gateway is officially open for teams requiring automated compute brokerage or specialized API routing. Submit an application directly through our site to get provisioned keys!

I'd love to hear feedback from the DEV community on our double-entry ledger schema, FastAPI route design, and routing setup.

Top comments (0)