Live demo
See it running before you install anything
These are real Sharelio components, rendered right now in your browser by the same engine that runs inside SharePoint. No sign-up, no tenant, nothing to install.
The only difference from your intranet is where the data comes from: here it is sample data, there it is your own SharePoint lists, read in the browser with each person's own session.
How Sharelio works, end to end
Three minutes, six chapters, no sign-up. Two of them render the real engine — the same one that runs inside SharePoint — rather than a picture of it.
Last edited 4 months ago
Someone in HR needs a holiday tracker on the intranet. Not a spreadsheet — something on the page everyone already opens, that reads a real SharePoint list and shows who is off next week.
Today that has two prices. A consultancy quotes €3,000–8,000 and 6–12 weeks, and then owns code you will pay to maintain every time Microsoft moves the framework. Or somebody makes a spreadsheet, emails it around, and within a month nobody trusts it.
In Sharelio you write what you need the way you would say it to a colleague. No functional spec, no ticket, no meeting.
The person writing this is the person who wants the tool — not a developer, not IT. That is the whole point: the distance between needing something and having it stops being a project.
Here is the part that decides whether IT will ever approve this: the AI does not write code. It writes a declarative JSON configuration — which list to read, which columns, how to format and filter them.
That configuration is validated against a closed schema before it is stored, and rejected outright if it does not fit. The schema cannot express code, evaluable expressions, HTML or arbitrary URLs. Nothing generated by a model ever executes inside your tenant.
You see it working with sample data before anything is published. Change your mind about a column, a filter or the order, say so, and it changes.
What you are looking at right now is the real engine, not a picture of it: the same renderer that runs inside SharePoint, with mock data instead of your lists. Counts and totals like these are the one thing SharePoint's free JSON formatting cannot do, because it cannot aggregate.
Your SharePoint administrator uploads one standard SPFx package to the App Catalog and approves one permission:
Sharelio / Components.Read, delegated and read-only. No Microsoft Graph, no access to your lists, files or mail, and no global administrator.This happens once per tenant, not once per component. After it, your team can publish fifty tools without a new deployment, a new permission or a new ticket. And your list data never leaves: it is read in each person's browser, with their own session and their own permissions.
The component sits on the intranet page like any other web part. It inherits the site theme, so it looks like your intranet rather than like someone else's product dropped into it.
From here it is a configuration, not a codebase. An extra column is a sentence, not a quote and a sprint. And if you ever remove Sharelio, the lists and their data stay exactly where they always were — in your tenant.
Chapters play automatically. You can jump to any of them, and everything written here is on the page whether it plays or not.
The four kinds of component, live
Tracker
The most common request: a list that people actually want to read. Search, filters and badges over a standard SharePoint list.
Described as“A maintenance incident tracker with priority, status, owner and cost, newest first, searchable and filtered by priority.”
Rendered by the same engine that runs inside SharePoint
KPI panel
Counts and totals — the one thing SharePoint's free JSON formatting cannot do, because it cannot aggregate.
Described as“A KPI panel over the incidents list showing how many are open, how many are in progress, and the total cost.”
Rendered by the same engine that runs inside SharePoint
Directory
The same data as a table, drawn to be recognised rather than compared — and readable on a phone.
Described as“A directory of the maintenance team as cards, with role, status and extension.”
Rendered by the same engine that runs inside SharePoint
Quick links
The least glamorous component and the most used one. Driven by a list, so it is edited without touching the page.
Described as“A quick links panel with the four things the maintenance team opens every day.”
Rendered by the same engine that runs inside SharePoint
Build one with your own data
The free plan keeps one published component, needs no card, and takes minutes. Your administrator installs one package, once — everything after that is yours to build.