Skip to content

Portal v0.24.0 — Hardened hosting, safer releases, and a public status page

Choose a tag to compare

View all tags
@AndrewDryga AndrewDryga released this 12 Jul 18:51
· 2231 commits to main since this release
Immutable release. Only release title and notes can be modified.
v0.24.0
This tag was signed with the committer’s verified signature.
AndrewDryga Andrew Dryga
GPG key ID: 73B7DDE1A8AC23B9
Verified
Learn about vigilant mode.
cd8952e
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

The hosted platform moved to hardened cloud infrastructure, and the release pipeline now proves what it ships.

Hosting & availability

  • The hosted control plane runs on hardened infrastructure: zero-downtime rolling deploys, a private-network database with TLS pinned to a private CA, and no public compute surface.
  • Availability is watched from outside the serving cloud, with on-call escalation behind a public status page at status.emisar.dev.

Release integrity

  • Portal releases publish the exact image exercised by CI, pinned by digest, with provenance and SBOM attestations; fixable HIGH/CRITICAL vulnerabilities block publication.
  • Binary releases are immutable and reproducible, and release tags are signed and verified before anything publishes.
  • Production infrastructure plans queue in order and never replace a review an operator already has open.

Pack registry

  • The registry serves from its own hostname, registry.emisar.dev, with anonymous access narrowed to exact object reads.
  • Publication verifies the exact object generation it wrote and checks pack tarballs end to end.

MCP

  • emisar's hosted MCP server (dev.emisar/emisar) is published to the official MCP registry.
Assets 3
Loading