01 / Scope
Ask inside a project, with its memory already loaded.
The chat sits beside the project's sources and its saved memory — typed notes on decisions, goals, and friction it already knows, not a blank slate.

Private beta / Bring your own model
AI chat that keeps notes on your work — typed, fading over time, and yours to edit.

How memory works
01 / Scope
The chat sits beside the project's sources and its saved memory — typed notes on decisions, goals, and friction it already knows, not a blank slate.

02 / Recall
Every note decays on its own half-life — a passing comment fades in weeks. Pin the ones that shouldn't.

03 / Inspect
Open citations, memories, files, and context receipts to see exactly what the response used — then fix any memory that's outdated or wrong.

04 / Resume
Come back to the project with its typed memory and conversations still organized around the work — nothing to retype, nothing forgotten that still matters.

Trust
Connect OpenAI, Anthropic, Google, or an OpenAI-compatible endpoint, billed by that provider at their rates. A limited number of invited testers instead run on a capped, Refinery-funded allowance.
Citations, memory, files, and context receipts stay visible so you can inspect what an answer used.
Provider keys are encrypted and app data is protected by Supabase row-level security. Refinery does not claim certifications.
Private beta
Request access, then connect your own supported model provider for beta use.
For most beta access, yes: connect your provider key before full chat and source indexing work. Memory features specifically need an OpenAI key today. A limited number of invited testers get a capped, Refinery-funded allowance instead and can skip this until it runs out.
Bring your own key: you connect your own OpenAI, Anthropic, or Google account and that provider bills you directly. That's the default for beta. A small number of invited testers instead run on a capped tester allowance funded by Refinery, up to a fixed cap, not unlimited or hidden.
Provider keys are encrypted, app data is protected by Supabase RLS, and you can already inspect, edit, or delete individual memories and see the sources behind any answer from the context panel. Refinery does not claim certifications.
The landing page is mobile-responsive. The product is desktop-first during beta; mobile app workflows come later.
Default beta access runs on your own model key, billed by that provider at their normal rates. A limited number of invited testers instead get a capped, Refinery-funded allowance at no cost to them. Hosted usage and paid plans are planned separately.
Chat runs on OpenAI, Anthropic, Google, or a custom OpenAI-compatible endpoint. Memory is different: indexing and recall currently need an OpenAI key, so an Anthropic-only or Google-only key gives you working chat without the memory features. Making memory work on any provider is in progress.
Existing export/delete surfaces are present but still need a full data-rights matrix. Public copy stays modest until that work is complete.
Canvas exists as a project work surface but is not the landing-page promise.