Skip to content

Built in the open ​

Inboxt is free, open-source, and designed to stay that way.

I originally built Inboxt to solve my own daily reading and information-management needs. There are many good tools in this space, but none of them quite matched how I wanted to read, save, and organize information. I wanted a read-later tool that respected my data, handled both articles and newsletters well, and stayed simple and transparent. I decided to build something that fit my own workflow. If your needs are similar to mine, Inboxt may be useful to you as well.

What “Built in the open” means ​

Open-source ​

Inboxt is fully open-source.

  • The source code is publicly available
  • Anyone can inspect how the app works
  • Contributions, bug reports, and discussions are welcome

Open development ​

Development happens in public.

  • Code changes are visible
  • Issues and bugs are tracked openly
  • Feedback is welcome and considered

Inboxt is developed and maintained by me, with community input helping shape improvements over time.

Self-hosted ​

You run Inboxt on your own infrastructure.

  • Full control over your data
  • No dependency on a central service
  • Suitable for individuals, teams, or organizations with specific requirements

No ads. No profiling. No lock-in. ​

Inboxt does NOT:

  • Show ads
  • Track user behavior for advertising or marketing
  • Lock your data behind proprietary formats

Your data is yours. You can export it or move your instance at any time.

License ​

Inboxt uses a dual-license structure:

  • Core Software: The API, web application, browser extension, and shared libraries are licensed under the AGPL-3.0. This ensures that improvements to the software remain free and available to the community.
  • Documentation: This documentation is licensed under the MIT License.

Third-party clients, integrations, and extensions that communicate with the server exclusively via the public API are not considered derivative works.

Follow the project ​

Development happens in public. You can follow along or participate here:

  • GitHub: source code, issues, and discussions
  • Roadmap: planned and in-progress work
  • Changelog: a history of changes and improvements

If you’re curious, want to contribute, or just want to understand how Inboxt is built, you’re welcome to look under the hood.