Pricing

Start with the right scope.

A useful pilot begins with your workflow, not a seat counter. We’ll work through the sources, access requirements and deployment you need, then agree on a proposal.

Open core

Run the core yourself, on your own infrastructure.

Free, MIT license

Read the developer guide

Includes

  • Self-host on your own infrastructure
  • Runs offline, no model API key required
  • Connect agents over MCP
  • Your operations, your support

Enterprise

For regulated teams that need it inside their own walls.

By agreement

Talk to us

Includes

  • Deployment in your infrastructure
  • Security and identity review with our team
  • Model provider of your choice
  • Support terms agreed in writing

No public per-seat or usage rate is offered during the private preview. Your proposal states every charge and limit before you begin.

A considered rollout

Make the first step measurable.

Agree on what a successful evaluation looks like before expanding to more teams.

  1. Map the need

    Bring a workflow where finding reliable context is slow or difficult.

  2. Define the pilot

    Choose the sources, access boundaries and questions you will evaluate.

  3. Agree the terms

    Review scope, pricing and support in a proposal before proceeding.

Questions, answered

Know what you’re signing up for.

Can I sign up and start immediately?

Slashh is in private preview. Contact us to discuss availability and the right scope for your environment.

What affects the proposal?

Source coverage, deployment requirements, usage, onboarding and support needs. Your proposal should make the applicable charges and limits clear.

Can we self-host?

The open core supports self-hosting. Operational requirements, model providers and enterprise support should be discussed separately from the software license.

Is every connector or feature included?

No blanket coverage is assumed. We confirm the sources and capabilities for your use case during scoping.

Will you need our production data for the first conversation?

No. Start with the workflow and your requirements. Any later data access should follow an agreed evaluation and security process.

A useful pilot starts with a conversation.

Tell us where company context is getting lost. We’ll help define a practical first step.