DIN 0815 · STANDARD SOFTWARE REV 2026.04 ● LIVE

DIN 0815/F3 · FOR LEGAL TEAMS

One licence.
One page.

MIT. No exceptions, no dual licensing, no hidden commercial terms. What your team needs to review is public and short.

Four sentences. No exceptions.

The MIT License grants permission to use, copy, modify, merge, publish, distribute, sublicense, and sell the software. There is no open-core carve-out, no commercial-use restriction, and no "enterprise edition" that triggers different terms.

No dual licensing.

Some vendors publish source under a permissive license and then sell a "commercial licence" for anything production-adjacent. We do not. MIT is MIT. Your use case does not change the terms.

Your data stays yours.

Software runs on your infrastructure. We do not process your data, host your database, or have any access to production systems after hand-off. There is no SaaS endpoint sending data home.

Source code audit, no request needed.

The repository is public. Your security team can audit it today, without signing an NDA, without a vendor review request, and without waiting for a SOC 2 report to arrive by email.

GDPR considerations.

Data processor role None — we are not a data processor once the software is handed off
Data residency You choose: your cloud, your region, your contract
Sub-processors Zero — no third-party SaaS dependencies in the module stack
DPA requirement Not applicable post-handoff; available on request for the build phase
Right to erasure You implement it — you have the schema and the code

The full MIT license text is on this site. If your review process requires a signed copy on company letterhead, write to hello@0815software.com. Questions about the build-phase DPA are answered the same way.

Read the MIT License →