Inlay Request early access

In alpha

An AI assistant that fits into your product.

Inlay is an assistant you embed for your own customers. It runs code on their data and answers with charts, spreadsheets and a written summary, in your brand and inside your app.

Request early access See how embedding works
Example: Inlay inside Fernway, a made-up subscription software company. The assistant carries Fernway's name, colours and type. Example data
Fernway
Fernway Assistant

Why did cancellations jump in week 3?

  • Read March's 18 cancellations and their accounts
  • Ran a Python analysis by plan
  • Searched the help article on plan prices

Week 3 had 8 cancellations, twice as many as week 2. Six were Starter accounts, just after the Starter price rose on March 14.

Cancellations by planExample data
Starter Team Business

What it does.

The work people now take to a general chatbot, done on the data already in your product.

Runs code on your data

It writes Python and runs it in a sandbox, so the numbers come from your data, not from a guess.

accounts.groupby("plan").mrr.sum()

Charts, spreadsheets and a summary

Answers come as charts and spreadsheets users can download, with a short written summary of what they show.

Sees what the user can see

It reaches your data through your MCP server or your REST API with that user's own token, so it has their permissions and nothing more.

Your help docs and the web

It searches your help articles for how your product works, and searches and reads the web for everything else.

Skills you publish

Package a job done your way, such as a quarterly account review, as a skill. Users can save their own from a chat.

Run from your console

Switch each tool on or off, choose the models, set credit limits per customer and read every conversation.

Looks like your product.

Name, icon, colours, fonts, corners and wording are yours. Users never see Inlay's brand. These three companies are made up.

Ledgerly AI

How much is overdue, and how late is it?

$48,300 is overdue, up from $46,000 last month. Most of it is less than 30 days late.

Overdue invoices, $kExample data
1–3031–6061–9090+
Ask Fieldbook

Which teams had the most repeat visits?

The North team had 14 repeat visits in October, twice as many as any other team.

Repeat visits by teamExample data
NorthEastSouthWest
NIGHTSHIFT / ASSIST

What caused last night's error spike?

Errors peaked at 02:00, twenty minutes after the 01:40 deploy. Nearly all came from the payments service.

Errors per hourExample data
00:0001:0002:0003:00

Coming soon

Work that runs on a schedule.

Users set up a task from the chat, such as a Monday summary of the accounts most likely to cancel. Each run picks up where the last one left off, and the result waits for them in your product.

When a run can't finish, it says so and says why.

Run historyExample data

Accounts at risk this week

Mon 2 Nov · 08:00 · Waiting in the assistant, unread

Delivered

Monthly overdue invoices report

Sun 1 Nov · 07:00 · Access to the billing data had ended. Open the assistant to reconnect.

Failed

One script tag and one endpoint.

Add the script to the pages your signed-in users see. Your endpoint, behind your own sign-in, asks Inlay for a session for that user. Your secret key stays on your server, and users never sign in twice. 

<script async
  src="https://embed.prod.inlay.chat/inlay.js"
  data-inlay-key="inlay_pk_live_..."
  data-session-url="/api/inlay/session"></script>

Put Inlay in your product.

Inlay is in alpha. Tell us what your product does and where an assistant would help.

Request early access