Juno API Launches as Self-Hosted Service for Developers

A new open-source API service for the Juno ecosystem has surfaced, aimed squarely at developers who want more control over how they run and secure their infrastructure. David Dal Busco, founder of Juno, flagged the release on X, calling it “a wild new repo” and pointing to its build with Bun and Elysia as an interesting technical pairing.

The project, simply called the Juno API, is designed to be self-hosted and deployed as a reusable Docker container. Rather than relying on centrally managed services, developers can run the API on their own infrastructure while staying compatible with Juno’s existing authentication and tooling. The approach reflects a broader preference among parts of the developer community for flexibility and clearer ownership of backend services.

At its core, the API focuses on authentication and identity support. Current features include GitHub OAuth proxy integration with JWT token generation, alongside a JWKS endpoint that allows public key discovery for token verification by Juno’s authentication modules. RSA keys are generated automatically when the container starts, each with its own key ID, reducing the need for manual key management during setup.

The project ships with a relatively straightforward quick start. Developers can deploy using Docker or Docker Compose after copying and configuring an environment file with their GitHub OAuth credentials and issuer details. Once running, the API is available locally on port 3000, with an OpenAPI specification and interactive documentation accessible via a browser. For those who prefer a more hands-on workflow, a local development setup using Bun and OpenSSL is also supported.

From a tooling perspective, the choice of Bun and Elysia is likely to attract attention. Bun continues to gain traction as an alternative JavaScript runtime, while Elysia positions itself as a lightweight framework focused on performance and developer experience. Whether that combination becomes a wider trend remains to be seen, but its use here signals a willingness to experiment with newer parts of the JavaScript ecosystem.

The repository is open to contributions, with clear guidance for forking, running checks and submitting pull requests. That openness suggests the API is intended to evolve alongside the needs of the Juno community, rather than remain a fixed utility.

While the Juno API does not attempt to solve every backend challenge, it offers a focused, infrastructure-first option for teams building on Juno who prefer to keep services close to home. As with any self-hosted solution, the trade-off is greater responsibility for deployment and maintenance, balanced against autonomy and transparency. For developers comfortable with that exchange, the project adds another practical piece to the growing Juno ecosystem.