Ashby HR & Recruiting

Connect Ashby


Dashboards, a full API and MCP access over your Ashby data. Hosted in Finland. Self-hostable, or buy the platform outright and run it yourself.

Portable technical infrastructure to any cloud.

A production-ready foundation designed to scale. Plug in pre-built modules for common workflows, or build your own on top.

Enterprise-grade from day one

Live from the first day, and portable later to any system. No vendor lock-in to Jourier: take the code, the schema and the models and run them yourself.

Hosted in Finland

Data and AI run in a Finnish data centre. UpCloud in Helsinki, and Mistral trained with CSC on the LUMI supercomputer in Kajaani.

Enterprise modular architecture

Scales to any level, from a new startup to a large enterprise. Build your own modules, or change the ones that ship.

The stack behind the unicorns

Talos Linux, Kubernetes and Cilium. GitOps deployments, a separate database per customer, automated security controls and self-healing.

Ashby dashboards

Time to hire, and where candidates drop

Time to hire, stage conversion and source quality are already built. Connect Ashby and they fill with your own pipeline. Where candidates drop out is read from stage history rather than reconstructed at the end of a quarter.

Ashby data in Jourier
Headcount, people cost and attrition on one screen.
Ashby data in Jourier
Finnish statutory cost broken out: TyEL, lomaraha, the rest.
Ashby data in Jourier
eNPS, absence and overtime against the cap.
Ashby data in Jourier
Employment type, work mode, age and tenure.
Ashby API

One API over Ashby and everything else

Most systems expose one API shaped around their own storage. Useful, but you build against that shape, handle its pagination, and repeat the exercise for every other system you own.

Jourier reads Ashby and serves the result as modelled JSON, on one endpoint, alongside every other system you connect. It is joined, typed and reconciled to what the dashboards show.

  • Roles, candidates, stages and headcount as first-class objects
  • The same numbers the dashboards use, from one definition
  • Read-only against Ashby; nothing is written back
Your data, your query
# time to hire and drop-off, by stage
GET /v1/people/funnel?period=2026-Q3

{
  "source": "ashby",
  "as_of":  "2026-08-16T06:12:00Z",
  "rows": [
    { "stage": "Tech screen", "entered": 48,
      "passed": 19, "avg_days": 9 }
  ]
}
Ashby MCP

Ask Claude about your own hiring

Model Context Protocol is how an AI assistant calls a real tool instead of guessing. Jourier exposes your connected systems as MCP tools, so Claude, Cursor or any MCP client can query Ashby directly, and answer from the hiring record rather than from a plausible sentence about it.

Every answer resolves to rows you can open. The model retrieves; it does not compute the number, which is the only reason the answer is worth having.

  • Works with Claude Desktop, Cursor, and any MCP-compatible client
  • Scoped to what that user is allowed to see; personal data stays governed
  • Self-hosted models available, so candidate data never leaves the EU
Claude · jourier
You
Where do candidates drop out,
and has it moved this quarter?

Claude
Tech screen, 60% drop. Up from 44%.
Same two interviewers on most of them.
Where the data lands

Ashby data in the tool you already use

Each has its own setup page: what syncs, how often, and what the schema looks like on arrival.

Connecting Ashby

Paste credentials, nothing to install

Access is granted per customer, so connecting is a matter of pasting keys. Nothing is installed and no port is opened.

What you'll need

Ashby API key
Secret
Access
Read only
Questions

Ashby and Jourier, answered

Can I get Ashby data into a dashboard?

Yes. Jourier reads Ashby and serves time to hire, stage conversion and source quality as dashboards that are already built. You connect Ashby and they fill with your own pipeline, so there is no modelling project first.

Does Jourier write anything back to Ashby?

No. The connection is read-only against Ashby. Nothing is written back.

Where is Ashby data stored when I use Jourier?

In Finland, on EU infrastructure, under EU law. The AI that reads it is self-hosted, so your data is never a US vendor’s training material.

How long does connecting Ashby take?

The connector is live. Connecting is a matter of pasting credentials: nothing is installed and no port is opened, and data flows the same day.

Can I use Ashby data from Claude or another AI tool?

Yes. Jourier exposes MCP tools, so Claude, Cursor or any MCP client can query Ashby directly and answer from the hiring record rather than from a plausible sentence about it. Access is scoped to what that user is allowed to see, which matters more here than anywhere else.

Can I run it on my own infrastructure?

Yes. It is standard Kubernetes built on open components. You can take the manifests and run it on your own cluster whenever you decide to, and there is no proprietary runtime holding you in.

Does this work with other systems as well as Ashby?

Yes. Jourier serves Ashby alongside every other system you connect, on one endpoint, joined, typed and reconciled to what the dashboards show.

Get started
Self-serve

Try the demo

Instant access to Jourier Lens. Business email only.