Slack
warehouse
Read-only by design
Writes are refused at the database, not left to the model.
Memory
Every investigation builds on the last.
Your team already knows which ideas worked and why others failed. Refix carries that history into its next recommendation, so your experience keeps informing the work.
Used by teams at
The more you work together, the better Refix knows your business.
-
Use your team's definitions
What counts as an active customer at your company becomes context for future questions across the team.
-
Keep up with the business
New information is checked against existing memory, so a changed definition can replace an outdated one.
-
Put earlier work to use
Findings and useful methods carry forward. The next investigation starts with more of the context your team has earned.
Keeping it current
When the business changes, its context should too.
If your definition of an active customer changes, future answers should reflect it. Refix checks new facts against existing ones and updates the relevant memory while keeping unrelated context.
- Replaces information that has been superseded
- Lets time-bound facts expire
- Update a fact or ask Refix to forget it
Better judgment
The right recommendation depends on what happened before.
A previous experiment may explain why an obvious change is a poor bet. Refix brings relevant history into the investigation and shows the context behind its recommendation.
- Relevant history recalled for the question
- Supporting memories available to review
- Business context carried between Home and Slack
Booking conversion reached 19.6% after the ranking change.
Completed bookings per search, Jul 6 to Aug 24
More of Refix
See how Refix finds an opportunity and follows it through.
- Watchers Growth goals followed through
- Sessions Work through a business question
- Investigations Find the cause and the next step
- Discovery Understands what your data means
- Charts Visual explanations your team can share
- Slack Work with Refix in the conversation
- Integrations Find opportunities across your tools
Security and control, built in.
Choose what Refix can access and set the approvals it needs. Review the data and reasoning behind its recommendations.
Approvals you control
Require your team's approval before Refix takes action in connected tools.
Roles for every teammate
Decide who connects data, approves actions, and manages billing.
Usage you can see
Daily credit use, with an alert before you reach your limit.
Zero data retention
Model providers keep nothing and never train on your data.
Self-hosting
Keep your business memory in your own cloud.
Run the Refix agent on your own Kubernetes cluster. Your platform team controls access and model connections, with our engineers helping you deploy.
- Helm chart for your Kubernetes cluster
- Your model keys or LLM gateway
- Slack sign-in or your identity provider
- Network access controlled by your firewall
- Application updates you approve
- Controls for reporting back to Refix
What does Refix remember?
Refix keeps business context such as metric definitions, past decisions, and useful findings. It also remembers personal preferences, such as how you want results presented.
Can I tell Refix to remember or forget something?
Yes. Ask Refix to remember a fact or forget something it has stored. For example, tell it that your team now reports revenue by week.
What happens when a fact changes?
Refix checks the new information against existing memory and updates what it supersedes. Facts with an end date can expire, so temporary context doesn't become a permanent assumption.
Is my personal memory shared with the team?
Personal preferences apply to your own conversations. Shared business facts, such as a metric definition, provide context for the team's work.
Where is memory stored?
Memory is stored in your workspace's database, isolated from other customers. With self-hosting, that database runs on your infrastructure.