Now building

We build automation you can see, share and rely on.

FRS builds AI software, automation and custom systems. For the last few years our research has gone into one thing: workflows on an infinite canvas that AI can run and people can trust.

order-intake
Orders today
128
Order value
$46,300
Waiting for a person
0

Most automation is fragile. It lives in one person's head, breaks without telling anyone, and cannot be handed over. We are working on the opposite: automation that is laid out in the open, written down, and runs the same way wherever you take it.

01Research

What we are working on

Five ideas we keep coming back to. Each one below is something you can try, not a picture of it.

Mini Map

01

Infinite canvas
A surface with no edges. A whole system is laid out in space: what it notices, how it decides, what it does and where it shows the result, with the notes that explain it next to the parts they explain. You see all of it at once instead of hunting through tabs and menus.
room-fanRun 128

Every few seconds

24.6°

Warmer than 28.0°?

No

Set the fan

Off

28.0°

Move the limit while it runs.

02

Workflows are the back end
Triggers, logic and actions, put together like blocks. Every block shows what it is doing while it runs, and when you change one, the next run uses it. There is nothing to rebuild or restart.

Server room

24.6°

Fan off

03

Overlays and dashboards are the front end
An overlay puts a result on the desktop, on top of whatever is open. A dashboard gathers the numbers and the controls on one page, and that page also opens in a browser, on another screen or a tablet.
The assistant wants to send

“Your order is confirmed. We will deliver it on Friday.”

04

AI that does the work
AI that reads, decides and acts through the tools you already use, not one that only answers. A person approves the steps that matter.
This computer
Running
Cloud

Try switching the cloud off.

05

Local-first
It runs on your own computer and keeps your data there. The cloud is for managing and connecting things, not something the work depends on.

02The standard

What automation should be

AI makes it easy to produce something that works once. These five are what we hold the result to.

01

Reliable
It does on the hundredth run what it did on the first, and tells you when it could not.

02

Documented
The explanation sits next to the workflow, not in one person's memory.

03

Shareable
A workflow can be handed to another person or team as one piece.

04

Reproducible
Copy a working setup and it works the same way somewhere else.

05

Stable
The environment it runs in does not change underneath it.
Glivo
Pre-releaseFor Windows
GGlobal
Beyond one device or one app: automation that runs across devices and systems.
LLink
Connects hardware, software, APIs, sensors and automation nodes.
IIntegration
Brings devices and services into one workflow, instead of each running on its own.
VVirtual / Visual
The logic is a visual workflow, and real-world devices are directed in software.
OOrchestration
Coordinates workflows, devices and the places they run, so together they finish complex tasks.

One piece of software any AI can use to reach the real world: your programs, your devices and your screen.

Let AI out of the chat window.

Glivo is a workflow engine on your desktop. It notices what happens, decides what to do, acts on your computer and your devices, and shows the result anywhere on your screen. And any AI can build all of it for you.

  1. Sense

    trigger

  2. Decide

    logic, AI

  3. Act

    action

  4. Show

    overlay, dashboard

  5. Loop back

    and again

01 Connect

Things never made to work together, working together.
A door sensor, a receipt printer, a fan, your shop's website and the screen in front of you know nothing about each other. In Glivo each of them is a block. Put the blocks together and they work as one, so a new job no longer needs its own script or its own project.

Putting the blocks together

  • Blocks, not scripts

    Devices, programs and logic are blocks joined by a line. What used to be a project of its own is now a workflow you can read at a glance.

  • Change it as you go

    Swap a block, add one or change a setting, then save. The next run uses the new version, with nothing to restart.

  • From your phone, or an AI

    Create a token and turn on remote access, and a dashboard opens in the browser of a phone on your network, its buttons starting workflows. Or switch on MCP and hand it to an AI, which can start and change them.

02 Build

An AI builds it. You watch.
MCPCLIHooks
Glivo speaks MCP, so Claude Code, Codex, Cursor or an agent of your own can read the built-in docs, look up the nodes, and build the database, the workflow and the dashboard while you watch. The same tools are there on the command line, and hooks send what your coding agent does back in as triggers. What an AI touched is marked, you choose how often it has to ask, and you can change any of it by hand.

01 / 08 You ask in your own AI assistant. Glivo has no chat box.

03 Overlay

A window without the window.

An overlay can be any shape, anywhere, on any screen, and clicks go straight through where it is empty. It is how AI gets out of the chat and onto your desktop.

01 / 05 Alert
  1. 01 Alert

    Someone at the door it does not know.

    The front-door camera sees a stranger, and the picture, with a box around them, appears over whatever you are doing.

    When the camera sees a stranger
  2. 02 Alarm

    A server stops answering while you are watching a film.

    A check that runs every minute gets no answer, and the alarm comes up over the film, on top of whatever is on the screen. The same goes for a full disk, a failed payment, or a door left open.

    When a check fails
  3. 03 Notice

    Your coding agent is done.

    A hook turns Claude Code finishing its turn into a trigger, so the result shows up on screen instead of in a terminal you are not watching. A few seconds later it closes by itself.

    When a coding agent finishes its turn
  4. 04 Shape

    It does not have to be a rectangle.

    An overlay can be any shape. This one is a character that lives on your desktop: pick it up and put it down somewhere else. Everything around it still takes your clicks.

    Started by hand
  5. 05 Break

    Five minutes off, on every screen.

    Every 50 minutes, an overlay covers every monitor, taskbar included, and counts down five minutes. It has no close button, only the time left, and when that runs out it lets you back in by itself.

    Every 50 minutes
Queued · 0Saved on disk
  • Nothing waiting
W1Free
W2Free
W3Free

0 completed · 0 tried again

04 Queue

However much comes in, nothing is dropped.
Runs started by a hotkey, a schedule, a webhook or a device go onto a queue that is saved on disk, and a few workers take from it in turn. A flood from one workflow slows nothing else down, a failure is tried again, and after a restart the queue carries on from where it stopped.
Hotkey pressed
—
Ask a model
—
Show the answer on screen
—

05 Try

Find out quickly whether an idea works.
Have an AI build it, set it off, and watch the result appear on screen. Every run is recorded step by step with its timings, so when something goes wrong you can see where.

claude · C:\shop

> Clear out the old build and build it again.

06 Hooks

Your coding agent can ask you first.
Claude Code, Codex and other agents send their hooks in as triggers: a turn finished, a session started, a tool about to run. A workflow can let a command through or stop it, and can put the question on your screen and wait for you. Glivo writes the hooks into the agent's settings, and shows you the change before it does.

Hotkey

Ctrl + Alt + K is pressedAsk a model about what is on the clipboard

07 Sensors

The computer is a sensor already.
A hotkey, a window coming to the front, you stepping away and coming back, the screen locking, the battery running low, a file landing in a folder, a USB drive, the network changing, a program starting: each can start a workflow, with no hardware to add.

08 Safety

The AI does the work. You keep the keys.
Glivo starts closed: it listens only on this computer, AI access is off, and what cannot be undone asks you first. Each of these you open yourself, as far as you choose.
  • Local by default

    Glivo listens only on this computer until you turn remote access on, and from then every request needs a token. Tokens are kept as hashes and can be revoked one at a time, and a dashboard can have a password of its own.

  • An AI can't raise its own permissions

    AI access is off until you switch it on, and you choose which tools an AI may call. Those choices, the tokens and remote access are settings no AI can change.

  • What can't be undone asks first

    By default, deleting rows, files or dashboards, or SQL that would lose data, waits for you to allow it. If nobody answers within two minutes, the answer is no.

  • Every AI change on record

    Each change an AI makes appears on the activity bar with what it was before, a changed setting comes with an Undo, and what an AI touched is marked.

  • Secrets stay secret

    Secret variables are encrypted on disk, with the key sealed by Windows. An AI reading a workflow sees [secret] where passwords and keys are, and an exported workflow leaves them out.

  • Checked before it runs

    A webhook can require a token or an HMAC signature, checked before anything runs, and a delivery sent twice runs once. Dry Run walks a workflow's whole path without touching anything real.

It also reaches

  • Keyboard and mouse
  • Windows and clipboard
  • Files and commands
  • HTTP
  • Webhooks
  • WebSocket
  • Serial ports
  • MQTT
  • HID
  • MIDI
  • OSC
  • Receipt printers
  • Home Assistant

It keeps its own database, so a workflow has somewhere to write things down. And what Glivo does not do, a plugin can.

Every signal becomes an action.

Runs on your computer · No account · Works without the internet

03Work

Our own products, and work for others

Glivo

Since 2026

Pre-release

What we are building now: a workflow engine on your desktop that any AI can build for you.

FransChat

Since 2022

Live
FransChat

Where our automation research began: automatic replies and message automation for Messenger and Instagram.

franschat.comMessengerInstagram

Custom work

We also build for other companies.

04Company

FRS began in 2020 in e-commerce and turned to software in 2022: websites and custom systems for clients, then our own products. For the last few years most of our work has gone into automation.

In software since
2022
Working on
AI, automation, local-first software
Products
Glivo, FransChat

05Contact

Tell us what you want to automate.

A few lines about what you have in mind is enough. We read every message and reply by email.

We use these details only to answer you, as our privacy policy explains.