Can OpenScion be a hosted service? The readiness checklist
Separate GPL licensing from operational readiness, and assess persistence, authorization, recovery, concurrency, and a realistic first pilot.
A commercial service is possible in principle, but the reviewed OpenScion revision is not a production repository hosting backend. Licensing and operational readiness are separate decisions. ScionHub currently publishes research and evaluation guidance; it does not accept or host repositories.
The audited snapshot is OpenScion v0.2.1 at 00e92ab9c2a9985f39a64636b4b6c5c4bb583916, reviewed October 14, 2026. Its source declares GPL-3.0-only, not AGPL. Workspace manifest
Understand the distribution boundary
GNU’s FAQ permits charging for GPL software. It distinguishes running modified GPL software on a server from distributing software to users: network use alone does not create the AGPL-style source offer requirement. Distributing a GPL-covered CLI, a customer deployment image, or GPL-covered browser JavaScript needs a separate compliance review and fulfillment of the applicable source and license obligations. GNU commercial-use FAQ, GNU server and JavaScript explanation
Those distinctions do not settle every combined-work or distribution question. Review the actual components and delivery method before shipping a paid package.
Prove the service fundamentals
| Gate | Evidence needed before private-code hosting |
|---|---|
| Durability | Acknowledged objects, changesets, and refs survive restart and failure |
| Recovery | A backup can restore a verifiable repository within a stated objective |
| Authorization | Denied reads and writes remain denied across every API and cache |
| Customer isolation | Tenant identity is enforced independently of client-supplied names |
| Concurrency | Ref conflicts, retries, and load have defined, tested behavior |
| Operations | Resource limits, telemetry, upgrades, export, and incident procedures exist |
At this revision, the server creates an empty in-memory repository when it starts. The router has no authentication middleware, and handlers share a repository-wide read/write lock. A reverse proxy can restrict access to a whole server, but it does not implement repository or directory permissions inside the application. Server initialization, API implementation
Our local smoke check reproduced unauthenticated ref reads and writes and loss of the previous ref after process restart. The test used disposable generated files on loopback HTTP; it was not an internet security assessment. Test evidence
Choose a smaller first pilot
An isolated demonstration using generated files is a reasonable way to explain the protocol today. A separate business experiment could retain GitHub or GitLab as the authority and serve immutable, permission-checked code slices to CI. That would require additional implementation; it is not a turnkey OpenScion feature.
Keep any pilot recoverable from the authoritative source, define what happens on cache failure, and measure against an optimized Git baseline. First establish a customer’s checkout bottleneck and willingness to pay. Then decide whether to build missing infrastructure, contribute upstream, or stop the experiment.