Build in public, only when it matters.
Arqora open source is not a dumping ground for experiments. It is a small, deliberate collection of tools, packages, and references that are stable enough to be useful outside our own systems.
01
Public package
02
Planned tools
03
Internal first
Registry
Public and candidate repositories
A compact index instead of marketing cards, so this page feels closer to a developer registry than the research page.
talkshitgetdared
Arqora repository
A lightweight truth-or-dare package built for developers, Discord bots, games, and custom party flows.
arqora-cdn
Arqora repository
A small upload, storage, and delivery layer for developer tools, bots, and internal Arqora systems.
arqora-labs
Arqora repository
Experimental utilities, infrastructure notes, prototypes, and proof-of-concepts before selective release.
Principles
What makes something Arqora-open-source
Useful before public
Projects are used internally first. Public release happens only when the tool has proven value beyond Arqora.
Safe by default
We avoid shipping tools that create abuse, privacy, or security risk without clear guardrails and documentation.
Readable over clever
Open-source code should be easy to inspect, fork, maintain, and understand without hidden context.
Small surface area
We prefer focused packages and clean APIs over oversized platforms that try to solve everything at once.
Contribution is welcome, not forced.
Arqora projects should be understandable without needing access to private systems. Contributions are reviewed for stability, maintainability, and whether they keep the project focused.
Contribution flow
Start with a focused change instead of a wide rewrite.
Explain behavior, tradeoffs, and breaking changes clearly.
Keep public packages stable before asking users to rely on them.
Changes are accepted when they improve the project without expanding it unnecessarily.
Licensing & trust
Clear licenses, clear boundaries.
Public repositories should include a license, README, usage notes, and responsible boundaries. If a tool depends on private infrastructure or internal assumptions, it stays private until it can stand alone.
License
Boundaries
Readable API
Contributors