licenses
Technical licenses.
apache 2.0
The public API specification and its schemas.
Open source in the ordinary sense. The license lets anyone read it, implement it, fork it, or run their own version. What it covers is the specification and the schemas, not access to the daps service itself.
elastic license 2.0
The platform code.
Source-available: the license allows reading, forking for development, auditing by anyone, and use for anything except offering the software to others as a hosted or managed service. A few narrow pieces stay closed: payment and royalty computation, licensed-content enforcement, and fraud detection. The test for adding to that list is whether opening it would put artist payouts, licensing obligations, or user safety at risk.
one condition, and why
Nobody sells access to what the community built.
Anyone may build against the daps API: a label, a newsroom, a university, a working developer, a fan. What is barred is making money out of the access itself, whether that is charging for what daps serves, reselling the catalog or the knowledge graph, or selling a product whose value is daps data.
keep me posted
The future of music is open.
daps is pre-launch and building in the open.