Referent

Work starts in chat

Chat is the front door to Referent. A user can ask a question in normal language, attach a file, dictate a request or start from a suggested task without learning another operations interface.

Referent can inspect live data under the user's existing permissions and cite the system behind an answer. When the user approves it, that answer can lead into an action or a workflow the team can run again.

Documents stay with the work

Uploaded files and generated documents live beside the assistant. Teams can find and organise material without moving to another tool between reading the information and acting on it.

Memory the team can inspect

Referent builds personal and organisational memory while people work. Search, entity relationships and a review queue turn useful details from one conversation into context the assistant can use later.

Connected to the existing stack

Referent connects email, calendars, storage, databases, commerce tools and other software where the work already happens. The assistant gets governed access to those systems instead of relying on another isolated copy of their data.

Connect where APIs stop

Browser Capture reaches custom portals and legacy software with no public API. It learns observed operations, keeps reads separate from approved writes and reports the health of each connection so browser automation isn't a black box.

Turn repeated work into a workflow

Teams can save a useful interaction as a workflow, test its inputs, schedule it and inspect previous runs instead of rebuilding the same sequence each time.

The platform supports single-tenant deployments, mirrored permissions, zero-retention model providers and configurable boundaries between read-only access and approved actions. It works against live systems rather than building a duplicate operational database.