Backend engineering
The backend job is the source of truth, and who is allowed to move it. Mine have been a GraphQL layer over blockchain events, a matching engine with browser-based signing, and a retrieval system behind a voice assistant.
Blockchain data and realtime APIs
I built ChainGraph as a GraphQL subscription toolkit for indexing and streaming EOSIO and Antelope data. At Bitlauncher I built the EOS EVM indexer on viem event subscriptions and a dFuse stream, with Supabase for queries, aggregation, and realtime subscriptions.
Exchange and protocol services
Bitcash needed the matching engine to be the system of record: Hasura GraphQL APIs, a realtime EOS indexer with worker threads and binary deserialization, and PostgreSQL behind the exchange. Opyn keeps protocol state in a Ponder indexer over PostgreSQL so the trading interface reads it instead of reconstructing it in the client.
Retrieval and application services
For LegalAgent the retrieval layer is an application service rather than a prompt. Document categorization decides what is eligible for retrieval, and system prompts are managed as data in the admin instead of shipped in code.
Writing about backend systems
See the work
Explore the project portfolio for implementation details, systems, and technology.




