A shared space for data
Just ask Neo.Run it locally. Tell Neo what you need. Local LLMs turn natural language into data workflows, and our C++ engine runs them on your machine. Clean, join, and chart your data automatically, with the freedom to inspect and change every step. Keep your work local. Share what you choose.
A shared view of the work. Coordinate the workflow and review its results in your browser.
Open cloud workspace ↗ Your data, on your machine. Clean and join local data with ET1, then turn the result into charts.
Explore desktop canvas ↗ Orders Two regions · 72 rows
Customers Names + segments
Products Products + pricing
THE RESULT Revenue by product
Summit
Atlas
Relay
Pulse
Studio
Different screens. The same shared work. Illustrated team roles
T Tyler Brings in the data
Desktop I Isabel Connects the tables
Desktop C Cody Builds the workflow
Desktop J Joel Reviews the data
Cloud S Silas Shares the charts
Cloud A Antoine Works with Neo
Desktop An example of the work coming together. Everyone contributes; each person has their own view.
From source to shared result
One workflow, from source to chart. See the joins, filters, and calculations behind every chart. Build the next step with your team.
Start with your data. Bring files and sources into the workspace. Organize what you need and choose what to share with your team.
Explore your data space Clean. Join. Make it yours. Connect tables, filter rows, and add calculations in ET1. Follow every step on the canvas, or ask Neo to help.
Explore workflows Give the answer a shape. Turn the finished data into charts and dashboards. Arrange the view, refine the details, and share what matters.
Explore dashboards Different screens. Shared work.
Cloud or desktop.Still on the same team. A place to bring the people in, and room for everyone to get to work.
In the cloud
n0is / shared workspace
I Bring the team in. Share the workflow. Keep the conversation close.
T I C J A S One shared space
Keep the team connected. Invite people into a shared room. Share workflows and results, discuss the next step, and keep the work in one place.
Open Collaborate Go deep with your data. Neo helps you work across your data, ET1 workflows, Rug, and charts using models on your machine. Keep your offline tools, and join your team when you’re ready.
Explore the desktop canvas Made to be shared
Embed a chart.Just add code. Take a published chart from your workspace to your website. Copy one tag and give the result a place to live.
The embedded resultPublic benchmark Compared engine neo in the same run
Zig 0.024 ms
neo in this run 0.020 ms
Swift 0.031 ms
neo in this run 0.020 ms
Rust 0.042 ms
neo in this run 0.020 ms
Go 0.079 ms
neo in this run 0.020 ms
Polars 1.546 ms
neo in this run 0.020 ms
DuckDB 2.239 ms
neo in this run 0.020 ms
pandas 12.239 ms
neo in this run 0.020 ms
Spark 38.959 ms
neo in this run 0.020 ms
One scale across all rows. Tiny bars are kept visible.
This is the published sum by region benchmark , rendered by the actual embed viewer.
The same public benchmark data , arranged for your phone. Open the full chart beside the embed code.
</> Your chart.One line of code.
JavaScript 01
<script async src="https://n0.is/embed.js" data-src="https://n0.is/embed/chart/sum" data-title="sum by region"></script>
↳ Ready for your page. This example uses a fixed public benchmark snapshot from n0.is.
Want it to update?Connect local output to an explicitly published live result. The optional connector watches your exported readout and sends changed display data.
01 Choose what to share. Publish the display data you choose. Your source workflow and connection credentials stay private.
02 Send changed results. The local connector sends an update only when the chart data changes.
03 Keep control. Publish explicitly. Revoke a live grant to remove its result from open viewers, too.
04 Use the work again. Embed an already computed chart or dashboard. Viewing it does not rerun your source aggregation.
Under the surface
A clear workspace. A capable engine. Explore the published engine comparisons, exact-output checks, and the cases where another engine is faster.
See the measurements Ahead in published comparisons 146 / 150 Head-to-head measurements
Over the JavaScript it replaces 33× Median across measured kernels
Same output, old and new 627 / 627 Exact-output verification cases