Our approach
Tools should make
room for your work.
AERIF™ brings focused applications together around a shared direction: local-first work, provider choice and decisions you can inspect.
One family. Distinct workspaces.
A lab for evaluating configurations needs a different shape from an audio arrangement or a knowledge workspace. Each AERIF product keeps the structure and vocabulary its work requires. Shared presentation helps you find your bearings without flattening those differences.
Local-first is a starting point.
Products are designed around local files and explicit execution boundaries. Available provider paths differ by application. A configured endpoint is not proof of a ready model; a browser interface may still be backed by a local service.
Evidence stays visible.
A simulated run is labeled simulated. A test tone is not speech. A proposed change is not accepted knowledge. Product pages explain what current UI and development evidence can establish, alongside what remains incomplete.
A direction, built in steps.
Today’s work spans Labs, Studios, Brain, Harness and an early Engine. Core, Runtime and Graph have distinct shared-foundation roles. AERIF OS is a longer-term concept, with no implementation or release date.
Local work. A separate Cloud direction.
AERIF Local is intended to be free for local use, with a planned source-available local release. AERIF Cloud is a separate future proprietary/private hosted service. Public source availability remains a later release gate; no final software license is announced here.