Skip to main content

Changelog

What Aestus shipped.

Public releases of the product and this site, newest first. Each one links to what changed.

Workspace Memory keeps accepted work in reach

Aestus now turns accepted work and direct human rules into cited claims that supported agents can recall, check, and correct.

  • Each claim links back to the task, document, artifact, or outcome that supports it.
  • The brief and relevant cited claims now reach board agents, workflows, permitted MCP clients, and governed Claude Code, Codex, and Pi sessions without crossing their audience boundary.
  • People can verify, correct, demote, retract, or purge a source lineage before it shapes later work.

Aestus Sandboxes enters early access

Invited teams can now run Claude Code and Codex in governed remote sessions, with the developer terminal kept local.

  • The Sandboxes page states what the developer keeps, what the organization keeps, and what a session leaves behind.
  • A policy window shows the seven surfaces one sandbox policy governs: repositories, network, credentials, MCP servers, skills, models, and spend.
  • Direct links in the main menu, home page, integration guides, and connector galleries make the early-access feature a first-class product surface.

The whole site now shares one register

Every public page was rebuilt in the Overcast register: night and paper bands, one real product window per scene, and live water under the plates.

  • Each page follows one band order, from hero to a closing band with its own verb.
  • Every scene holds one real product window, fed by the same Meridian workflow and replaying its morning.
  • Sea plates render a live ocean on WebGPU, one sea state per plate. Reduced motion holds a still frame; browsers without WebGPU keep a still plate.
  • Each page has a contract test that pins its band order, windows, translation scope, and word budget.

Every part of the product now has a public page

The rebuilt site explains how Aestus connects shared work, orchestration, systems, policy, and completion cost.

  • The homepage follows one governed workflow from goal to verified result.
  • Workspace, orchestration, connectivity, optimization, security, pricing, and about pages each explain one part of the product.
  • Six integration guides cover setup, approval boundaries, recorded evidence, and the cost of a disclosed example run.
  • Canonical metadata, social images, structured data, a sitemap, and crawler rules for private routes ship together.

One public site, built from the real product

Separate marketing fragments became one responsive site with one copy source and product windows fed by real fixtures.

  • Shared navigation, footer, calls to action, theme controls, and reduced-motion behavior serve every public page.
  • Product demos use one checked-in Meridian workflow, so cards, people, agents, policy, and run evidence stay consistent.
  • Public copy lives in maintained site messages, with contract checks that catch missing or hard-coded text.
  • First-party conversion events measure navigation and waitlist intent without collecting typed email addresses.

See the next release from the inside.

No spam. One email when your slot opens.

Talk to us