About This Blog
This is the engineering blog for Jupiter's developer platform. It's written by the people who build the systems — routing, infrastructure, APIs — not a content team.
What you'll find here
We write about the problems we solve and the decisions we make along the way. That means:
- Deep dives into how things work under the hood — routing engines, transaction pipelines, pricing algorithms
- Practical guides for developers building on our APIs — patterns, pitfalls, and working code
- Tutorials that walk through real integrations step by step
Why we write
Building in public keeps us honest. When we explain a system, we find the gaps in our own understanding. When we document a pattern, we commit to maintaining it. Writing is how we think clearly about what we've built and what we should build next.
Who writes
Engineers. The person explaining split routing is the one who implemented it. The person writing about rate limits designed the throttling system. We believe the best technical writing comes from the people closest to the code.
If you're building with Jupiter, this blog is for you. If you have questions or want to go deeper on a topic, reach out — we're listening.