Venapce

Logic is FloMorphic. Venapce is the view.

This is the split that defines the whole product. Every piece of business logic in Venapce lives in a FloMorphic workflow — collection, correlation, evaluation per feature, and the LLM reasoning that turns a pile of frames into a recommendation. FloMorphic is where the thinking happens.

Venapce itself holds no security logic. It reaches FloMorphic through plugins and delegates the thinking to it. What's left is the face: a posture builder, a fleet view, an issue list, and a BI surface — the panel you operate from.

collect · correlate · reason · present & act — Venapce owns the last step and nothing before it. The intelligence is never trapped inside the UI; it lives in a graph you can open, read, and change.

Senses you can trust because they're dumb. Judgment you can trust because you can read the graph. A posture you can act on because it's right in front of you.

Stage → Issues

Two tables carry the whole model, and they're the clearest way to understand what Venapce does. Between them sits FloMorphic, doing the data engineering: correlate, enrich, drop the false positives, promote the real thing.

Over both tables sits a full BI chart and dashboard builder — every chart drawn on data that came from FloMorphic. Posture isn't a fixed set of screens; you build the views you need. Everything is dynamic: each feature is a flow, built and optimized inside FloMorphic's workflows rather than hardcoded into the product.

One image, one database

Venapce ships as a single container image. Inside it are four things that work together — and behind them, one Postgres. A security posture layer you can stand up without assembling five services by hand.

The vein is agents

The core sense — the one Venapce is named around — is the endpoint fleet. Lightweight osquery agents run across all of your compute and stream what they see back up, into a node hub that enrolls them and collects it. The agents are the pathways, threaded through every system you own — the vein, made literal.

The panel carries a menu of enrolled operating systems and their live status, so you can see the fleet itself — who's reporting, who's gone quiet — before you ever look at a finding. And onboarding should feel like plugging in, not standing up infrastructure, so there are two paths.

Either way you land in the same place: a live fleet view of every enrolled node, with the workflows already reasoning over what those nodes report. Fast bootstrap for people who want to see something today — and a clean bridge to your own infrastructure when you're ready to own it.

It acts on issues — and only issues

Because every feature is a flow, some of those flows carry an AI node — and that turns into an assistant. A narrow, well-behaved one. It doesn't roam your estate. It acts on a single issue, on demand: you click an issue, the workflow runs, and the AI works that issue the way a person would — reading the context, taking the steps — but bounded by the flow that was designed for it.

It does exactly what the graph allows: not more, not less, and no false-positive action. It isn't an autonomous agent making its own decisions about your infrastructure; it's judgment applied to one issue, inside a contract you drew.

The intelligence acts — but only where you pointed it, and only how the flow permits.

Sense broadly, reason in the open

Honest status, because it matters. One sense is confirmed and next to land; the rest are in feasibility study. A collector that holds no logic and no secrets is one you can trust and reuse — every plugin speaks one protocol, inflowv1, so a sense written once runs on any host that implements it.

Anything else — a ticketing system, an ITSM API, an endpoint-context source — is just an ordinary integration plugin, wired in when a feature needs it. It isn't part of what Venapce is. The core is the osquery fleet; everything else is a sense you can add.