Ops command deck · Liquid Design

We automate work with AI agents connected to all the sources that matter.

At Liquid Design we build balanced agents that combine monitoring, ticketing, code repos and internal data — so they actually take over the routine, instead of adding another dashboard. LQDeck is our ops command deck, where every project surfaces side by side.

LQDeck — built by Liquid Design. Twenty years of bespoke development, now wired into AI agents.

Meet Liquid Design
The decks

Cron · Errors · Uptime · Triage. One deck.

Every module is its own deck with a status light and a key metric. You see them side by side — not across five open tabs.

deck/01 · cron Nominal
142 runs / 24h

Cron Deck

Schedule, queue, retry. Watches every run, respects concurrency limits per project and per job, catches runaway timeouts.

deck/02 · errors Watching
3 novel / 24h

Error Deck

Captures errors from your Nette apps, groups them, filters noise with ignore rules. Slack only pings when a threshold actually fires.

deck/03 · uptime Online
99.96 % / 30d

Uptime Deck

Probes project URLs on a schedule, logs downtime windows, integrates Freshping callbacks. Recovery is timestamped, never guessed.

deck/04 · triage 7 queued
7 awaiting review

Triage Deck

An AI agent reads Freelo tasks and monitor data, drafts an analysis and queues it for your review. Kill switch sits one click away.

Our approach

A balanced agent does more than a chatbot — because it sees the whole context.

Instead of isolated tools and one-shot prompts, we build agents with live access to monitoring, task trackers, repositories and historical decisions.

01 · See

The agent reads everything

No tab-switching. The agent reads production logs, error tracking, queued jobs, open tickets and recent deploys — all under one authentication.

LQDeck Freelo Slack repo
02 · Decide

Triage before you look

The agent classifies tasks, drafts a response or a path forward, estimates effort. You approve and edit — no re-reading every new ticket from scratch.

Claude Cursor review queue
03 · Act

Actions flow back into the systems

An approved result returns to Freelo, Slack or the repo as a comment, draft commit or assignment. Human sign-off stays — autonomy lives only where it earns its keep.

handoff audit log kill switch
API surface

Talk to it over HTTP

Four endpoint groups — each for a different kind of client, each with its own authentication. Full reference at /docs/api.

/api/connector Job lifecycle from your Nette runner — schedule, start, progress, finish, fail.
connector
/api/triage Triage tasks, results, job-runs and the global pause flag for the orchestrator.
scoped key
/api/front Read-side REST for projects, crons, jobs and errors. Session authentication.
session
/api/freshping Inbound webhook for Freshping up/down events.
webhook

Want this kind of automation for your project?

We help companies build agents that take over the routine work without losing quality. Wired into your internal systems, under your control.