SOURCE TO RELEASE

Good releases
are woven together.

Trusted release infrastructure: connect pinned source, isolated builds, evidence, publisher identity and deliberate promotion.

Development preview. Not a production service.

THE RELEASE THREAD01 — 03
01SourcePin what goes in↗
02ReviewCheck the evidence◇
03ReleaseDeliver checked bytes→
BUILT AROUND REVIEW

A MORE CONSIDERED PATH

One thread from
source to release.

Release delivery involves more than storage. PkgLoom connects source discovery, release definitions, artifact evidence and human approval—without treating a successful build as a production guarantee. The publisher or platform signs the software; Blackout Secure verification is a separate assertion about measured evidence.

01 / CONNECT

Start with your source.

Review a pinned snapshot and discover projects without running customer code on the control plane.

02 / VERIFY

Keep evidence close.

Bind policy and approvals to the exact artifacts under review. Missing evidence is not a pass.

03 / DELIVER

Make intent explicit.

Keep visibility and destinations separate, with reviewed actions instead of silent publication.

MULTIPLE ECOSYSTEMS, ONE WORKFLOW

Built for the work
between ecosystems.

Different package formats need different protocols. Client qualification and production readiness are tracked separately.

Native first FreeBSD · OpenWrt APKLegacy OpenWrt OPKG / IPK compatibilityPython PyPIContainers OCIJavaScript npmLinux Debian · CondaJVM Maven · Gradle

A DISTINCT MOBILE ADD-ON

Test privately.
Promote deliberately.

Android Play testing and Apple TestFlight are planned release-operations workflows, not two more package formats. Typed planning is available in development; live builds, signing and store automation are not enabled. Customer-owned accounts remain the publisher.

01 / ANDROID

Separate the keys.

Plan around Play App Signing and a separate customer upload identity. Internal, closed and open testing can lead to production. Managed Google Play private-to-public requires a different package name.

02 / APPLE

Keep publisher ownership.

Prefer customer-controlled or supported Apple cloud-managed signing. TestFlight can precede App Store review. Custom Apps are managed private; changing private/public distribution requires a new app record. Unlisted is not private.

03 / VERIFIED RELEASE

Two signatures. Two claims.

A future Blackout Secure attestation will name the exact artifact or store build, policy version, checks, exceptions, validity and revocation. It is detached from the app signature—not a certified-secure badge or a warranty.

PLANNING, NOT BILLING

Draft plans, clearly labeled.

Provisional monthly organization pricing. Billing is inactive; managed compute and AI are separately metered only after rates are approved.

Free

$0 / month

1 GiB storage · public open-source packages · customer-operated builds

Developer

$19 / month

10 GiB storage · 1 operator · public and private packages

Team

$79 / month

50 GiB storage · 5 operators · team policy workflows

Business

$249 / month

200 GiB storage · 15 operators · advanced integration options

Plans are drafts, not an offer or a promise of availability. Retained source and snapshots count toward storage. Mobile capacity, store automation, independent verification and qualified signing are separate planned add-ons; no unlimited macOS builds or managed keys are included. Managed-custody pricing requires measured cost and independent review.

WHERE THINGS STAND

Built carefully. Still in progress.

PkgLoom is a local development implementation, not a production multi-tenant service. OpenWrt and FreeBSD native conformance remain the package MVP priority. Mobile planning does not qualify a signer or activate a store connector. Identity, isolated workers, signing and live hosting need further qualification. No format is advertised as production-qualified by local fixtures.