About
More time for the product that is yours.
We are building Inlay for founders and developers turning agents into products people use. Our focus is the backend beneath that experience, from designing the agent to running it for your users.
Why Inlay exists
An agent demo is not the whole product.
A working prompt is a starting point. A product also needs an interface, controlled access, state, a way to inspect what happened, and an understanding of what each user consumes. Those concerns quickly become entangled with the agent itself.
Inlay brings a visual graph, a Rust execution core, and the surrounding agent infrastructure into one system. The goal is to make less of your product depend on custom orchestration and integration code, and more of it depend on what you understand about your users.
Inlay / canvasScreenshot placeholder
The graph behind your product
Trip Planner canvas: a brief, flight lookup, parallel specialists, and an itinerary-to-map hand-off. Include the published version.
Capture / canvas.webp2400 x 1350 px
A backend, not your brand
The experience belongs to you.
You build the interface, product logic, sign-in, and authorization. You choose which agent outputs become part of the experience and what users can do with them. Inlay provides the graph, execution, and SDK surfaces those decisions connect to.
That can be a research workspace, a guided planning product, or an agent working behind an existing interface. It does not have to look like a chat window. See the platform and developer guides for the pieces you can build with.
Where we are today
Private beta. Manual onboarding.
Inlay is early. Access requests are reviewed manually, and onboarding is a conversation about the product you want to build, the current platform, and the gaps that matter to your workload. A request is not an automatic account or a guaranteed invitation.
Launch rates are pending. Feature access, limits, and commercial terms need to be discussed during onboarding; this site does not offer free or unrestricted beta use. The docs describe the current integration surfaces and their limits.
Start with your product
Who is it for? What should the agent do?
Use Request access to describe your product and where you are in building it. A short description is enough to begin; do not send credentials or private customer data. If you are already in contact with us, continue in your onboarding conversation.
Build the product only you can build.
Tell us who it's for and what the agent needs to do. Inlay is in private beta, with access reviewed and onboarding handled manually.