What is Vibe?
Vibe lets you get a small, custom app built on top of the Facilio data you already have — usually in a fraction of the time a normal software project takes.
You describe the tool you want. Someone builds it — increasingly, an AI assistant does most of the work. What comes back is a link. You open the link, sign in with your normal Facilio account, and the tool is there.
No app store, no installation, nothing for IT to roll out. Just a web address.
This page is written for people who will never open a terminal. There is no code on it.
A concrete example#
Say your team reviews vendor performance every month, and today that means exporting work orders into a spreadsheet and building the same summary by hand.
With Vibe, you'd ask for: "a page that lists every vendor, how many work orders they closed last month, how many were late, and their average response time — sorted worst first."
What you get back is a page at an address like https://vendor-scorecard.vibe.facilio.com. It reads live from Facilio, so it is never out of date, and anyone you share it with sees the same numbers. The monthly export is gone.
That's the shape of every Vibe app: a focused tool that does one job well, using data that already lives in Facilio.
What people build with it#
- Dashboards — KPIs for a site, a region, or a single client, showing exactly the numbers that matter to that audience.
- Simplified screens for the field — one big form for a technician doing inspections, instead of navigating the full product on a phone.
- Portals for people outside your team — a tenant checks the status of their request; a vendor sees only their own jobs.
- Internal clean-up tools — bulk-fix bad records, review a data-quality queue, approve a batch of items.
- Reports that assemble themselves — a digest that lands every morning with no one running an export.
The common thread: something your team currently does by hand, on a schedule, in a spreadsheet.
What a Vibe app can do#
| It can… | Meaning in practice |
|---|---|
| Read and write your Facilio data | Work orders, assets, sites, tenants, vendors — see them, and create or update them from the app. |
| Reach your other business systems | Accounting, CRM, HR and similar tools can be connected, so one screen shows what is currently spread across several. |
| Keep its own records | Data that belongs to this tool alone, and doesn't fit the main Facilio model, has somewhere to live. |
| Accept photos and documents | A technician attaches a photo; an approver opens a PDF. |
| Use AI where it helps | Summarize a long history, sort incoming requests by type, read a number off a photographed meter, pull fields out of an invoice. |
| Do work on a schedule | Check something every morning and email or flag what needs attention — without anyone opening the app. |
| Update itself as things change | A shared screen can refresh the moment someone else makes a change, so two people are never looking at different numbers. |
What it is not#
Being clear about the edges saves disappointment later:
- It is not a change to Facilio itself. A Vibe app sits alongside the product and reads the same data. It doesn't alter your modules, fields, or workflows.
- It is not a spreadsheet replacement for everything. It suits a repeated, defined job. A one-off ad-hoc analysis is usually still faster in a spreadsheet.
- It does not build itself from nothing. Someone — a developer, or an AI assistant working from your description — still has to build it. What Vibe removes is the hosting, sign-in, and data-plumbing work that used to make small tools not worth doing.
- It is not automatically safe to publish widely. Access is a decision someone makes deliberately (see below), not something to assume.
How one actually gets built#
- You describe what you want — in plain sentences, the way you'd explain it to a colleague. What should it show, who is it for, what should someone be able to do on it.
- It gets built. Either a developer picks it up, or an AI assistant does most of the work from your description. This is where Vibe's real advantage is: the assistant can go from your description to a working link on its own.
- One approval click. At one point in the process, a browser window asks the person building it to approve access to your Facilio account. That single click is the only manual step in the whole pipeline.
- You get a preview link and try it. Say what's wrong or missing — "group this by site", "the date is in the wrong format", "add a filter for open only". Changes are quick, because there's no release process to wait for.
- It goes live at its own address, shared with whoever should have it.
Step 4 is the one worth planning for. Nobody describes a tool perfectly the first time, and Vibe assumes that: the loop from feedback to a new version is short by design, so it is normal — not a failure — for the first version to need three rounds of adjustment.
Who can see it#
Every app has a preview version and a live version. Preview is where changes are tried; live is what your audience uses. They are kept separate on purpose, so work in progress never disturbs people using the real thing.
For access, there are two broad choices:
- Signed-in users only — people open the link and sign in with their normal Facilio account. This is the default, and the right answer for anything internal.
- Open to anyone with the link — for a public form, a status page, or something shared with people who have no Facilio login.
That second option is a real decision, not a formality: anyone with the link can see the app, so a public app must not show data belonging to one specific customer or person. If you are unsure which mode a tool needs, that is the right question to raise with whoever builds it.
Words you'll hear#
You don't need these to use a Vibe app, but they come up in conversation:
| Word | What it means |
|---|---|
| App | The tool itself — one link, one purpose. |
| Deploy | Publishing a new version. Takes seconds, happens often. |
| Preview / live | The version being worked on, versus the one your audience uses. |
| Connection | A link to a system holding data — Facilio itself, or another business tool. |
| Function | A piece of logic that runs on the server rather than in the browser, so it can be trusted with the sensitive parts. |
| Job | Something the app does on a schedule, with nobody watching. |
| Agent | An AI step inside the app — summarizing, classifying, reading a document. |
| Realtime | The app updating on its own when data changes, instead of you refreshing. |
What to do next#
If you work at Facilio#
Your job in a Vibe conversation is usually to scope the tool, not to build it. The most useful things you can bring back are: who the users are, the one job the tool must do, which data it needs, and whether anyone without a Facilio login has to see it.
A good scope is narrow. "A screen for the duty manager showing today's overdue work orders by site" gets built and used; "a portal for everything the ops team needs" turns into a project. When a request grows past one clear job, split it into separate apps.
Hand the description to a developer, or to an AI assistant pointed at Building with AI Agents — which is written for exactly that handoff.
If you're a Facilio customer#
Bring the tool you want to your Facilio contact, described the way you'd explain it to a new colleague: what it should show, who will use it, what they should be able to do. You do not need to know what is technically possible — that's the conversation, and "can Facilio data do this?" is a fair opening question.
Two things worth stating up front, because they shape everything: who must be able to open it (your team only, or people outside), and what decision it should make easier. A tool built around a decision gets used; a tool built around a data dump usually doesn't.
If you're technical, or curious#
The rest of this section is the developer documentation:
- Overview — the same picture, in technical terms
- Getting Started — build and ship one yourself
- Building with AI Agents — hand the whole job to an AI assistant