Slack
warehouse
Read-only by design
Writes are refused at the database, not left to the model.
Sessions
Get to the answer behind the numbers.
Ask why customers aren't returning, or whether a new market is growing profitably. Refix investigates across your connected tools and brings back an answer your team can use.
Used by teams at
Bring the question. Refix does the investigation.
-
Ask in your own words
Start in Home or Slack. You don't need to know which table holds the answer.
-
Follow the question further
Refix breaks the work into steps and follows the evidence across sources as the answer takes shape.
-
Make an informed call
Review the finding and the evidence behind it. Ask a follow-up when you need to understand more.
Across your tools
The answer may be spread across your tools.
Product analytics shows growing interest. Your database shows flat bookings. Refix connects the two and checks payments to understand where the journey breaks down.
- Uses the relationships found across your sources
- Investigates with read-only data access
- Clarifies the question when it needs more context
A conversation you can build on
Ask the next question. The context is already there.
Once you know where the problem is, ask which customers it affects or what to try next. The session keeps the investigation together, so you can go deeper without explaining it again.
- Charts that explain the finding
- Supporting queries and sources to review
- Share the answer with the team taking it forward
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
- Investigations Find the cause and the next step
- Discovery Understands what your data means
- Memory Builds on what your team has learned
- 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
Get answers on your own infrastructure.
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
Questions about sessions.
Asking questions, reviewing evidence, and picking up where you left off.
Talk to a human What is a session in Refix?
A session keeps your conversation and the investigation behind it in one place. Return to an earlier answer, inspect the evidence, or ask a follow-up.
Where can I ask Refix a question?
Ask in Home, send Refix a Slack DM, or mention it in a channel it has joined. Your past sessions are available in Refix.
How does Refix know which data to query?
Refix uses its understanding of your connected sources and your team's definitions to choose the relevant data. It builds that understanding through Discovery and Memory.
What happens when my question is unclear?
Refix asks for clarification when it needs more context to investigate. You can also correct its direction as the conversation continues.
Can Refix change our data while it answers?
Analytics and database investigations use read-only access. Actions in other connected tools follow your workspace's approval settings.