Crafted, not assembled.

Doxa (δόξα) — Ancient Greek for glory, radiance, splendor. Inspired by the artisans of Exodus 31, who were filled with wisdom, understanding, and skill to build something worthy, Doxa Labs is a collective of builders who believe great software is made with care, shared generously, and refined relentlessly.

We're part open-source workshop, part product studio, part learning community.

We build developer tools, platforms, and products — software infrastructure designed for real workflows and real users. We also rebuild popular tutorials in modern frameworks, create open-source libraries focused on correctness and less dependencies (sometimes zero), and share everything we learn along the way.

Some of what we ship is open source. Some is paid. All of it is crafted with intention.

Browse our work — Repositories · Projects · Open Source

• Crafted with care — Every decision is deliberate. We sweat the details because the details are where quality lives.
• Open by default — We share our code, our process, and our lessons. The first commit is public. Open source isn't a strategy — it's how we believe good software should be made.
• Built to last — We choose boring technology over hype. We write tests. We document. We build things that work today and still work a year from now.

We prioritize simplicity, performance, and developer ergonomics. Our stack is selected to support fast iteration, strong typing, and high performance for both end-users and developers. Read more in our tech stack guide.

We welcome contributions across all our projects. Before diving in, take a look at our coding conventions and style guides:

• JavaScript Style Guide — Naming conventions, import structure, JSDoc patterns, and best practices
• Go Style Guide — Naming conventions, project layout, error handling, and best practices
• Svelte Style Guide — Component conventions, runes usage, and best practices
• Dart Style Guide — Naming conventions, Flutter widget patterns, and best practices
• Python Style Guide — PEP 8 conventions, docstrings, type hints, and best practices
• Zig Style Guide — Naming conventions, memory management, and best practices
• Rust Style Guide — Naming conventions, error handling, and best practices
• C Style Guide — Naming conventions, memory management, and best practices
• Tech Stack — Languages, frameworks, and tools we use

Our standards: clarity over cleverness, tests are not optional (not always), small PRs ship faster, and be kind. Code review is a conversation, not a judgment.

Our open-source projects are licensed under MIT or Apache 2.0, unless otherwise stated in the repository. Check the LICENSE file in each repo for specifics.

Have a question, idea, or just want to say hi? Here's where to find us:

• GitHub Discussions — For project-specific questions, proposals, and conversations. Open a discussion in the relevant repo.
• Discord — Join our Discord server for real-time chat, help, and community.
• X (Twitter) — Follow @doxalabs for updates, releases, and the occasional hot take.

For bugs and feature requests, please use GitHub Issues on the relevant repository.

Website · Blog · Open Source · Careers

Contact — hello@doxalabs.com