Relpin publishes content-addressed releases: every publish canonicalizes the bundle, hashes it with SHA-256, and pins it to exact platform and org schema versions. The same artifact is promoted across environments instead of rebuilt.
identical content re-publishes as a no-op · version records append-only
Most internal tool platforms ship whatever the editor currently holds. A deterministic release pins an exact artifact hash to an exact schema version, so what was reviewed in TEST is byte-for-byte what runs in PROD.
Every publish canonicalizes the bundle to stable JSON and hashes it with SHA-256. The hash is the identity of the release, so identical content re-publishes as a no-op and there is no ambiguity about which artifact a version record points to.
Version records are append-only and pinned to the exact platform version and org schema version they were built against. A release is not a moving pointer to the latest editor state; it is a fixed artifact tied to the schema it expects.
DEV, TEST, and PROD share one content-addressed artifact. Promotion clones that exact artifact to the target environment instead of rebuilding, and fails closed on schema drift re-verified at apply time. Approvals are bound to the artifact hash, so re-planning invalidates them.
All category guides for internal tool builders, AI agents, low-code limits, and production data.
Governed Internal ToolsHow pinned releases fit the broader governance model.
Audit-Ready Internal ToolsHow promotion decisions are audited alongside data changes.
Retool AlternativeCompare release pinning with a visual internal tool platform.
Platform GlossaryDefinitions for the release and governance terms used here.
In Relpin, a deterministic release is a content-addressed artifact: every publish canonicalizes the bundle to stable JSON, SHA-256 hashes it, and pins the version record to exact platform and org schema versions. The same artifact is promoted across environments rather than rebuilt.
Because releases are content-addressed, identical content produces the same SHA-256 hash and re-publishes as a no-op. A new version record is only created when the canonicalized bundle actually changes.
Deployment pointers are forward-only; there is no rollback operation. Releases are pinned and promoted forward through DEV, TEST, and PROD, and promotion fails closed on schema drift re-verified at apply time.