Venapce
A nervous system for security governance
Every security team is drowning in tools and starved of connective tissue. Endpoints, network gear, cloud consoles, the ticketing system — each is a black box that already decided what matters, and none of them talk. Venapce is the missing layer.
Past its feasibility study and in active development, Venapce is the first product built the FloMorphic way, end to end: all of its business logic lives in workflows, and Venapce itself is only the view — the posture you see and the panel you act from.
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 is posture and presentation — the face. Dashboards, fleet view, issue list, the panel you operate from. It shows you what the workflows concluded and gives you the surface to act on it.
Reach each system, return raw data frames. No opinions, no scoring, no stored secrets.
Frames → document store → correlate & evaluate per feature → an LLM node reasons in the open. All business logic lives here.
Dashboards, fleet view, issues, actions. Posture you can see; a panel you act 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.
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.
Go backend
The service the panel talks to, and the bridge to FloMorphic. It orchestrates workflows and serves what they produced — it holds no security logic of its own.
Vue web app
The panel itself: fleet, posture, issues, and the osctrl onboarding flow. The surface you operate from.
Superset builder
Posture isn't a fixed set of screens I chose for you. Build and shape the dashboards you need over the data the workflows produce.
nginx
Ties the web app, the API, and Superset together behind one origin.
One Postgres, shared by Superset and the backend API. That's the whole footprint. Swap a workflow and the product's behavior changes without a rebuild — the payoff of putting all the logic in the graph.
Onboarding through osctrl
The core sense — the one Venapce is named around — is OSCTRL, managing an osquery fleet through osctrl. Watching your endpoints is where the vein metaphor gets literal, and onboarding should feel like plugging in — not standing up infrastructure. The panel gives you two paths.
Connect your own
on-premAlready running osctrl on-prem? Point Venapce at it. The panel connects, and your enrolled nodes start showing up.
Request a space
hostedNo osctrl yet? Ask for one from the panel. Inflowenger runs osctrl on its own servers; a request provisions a dedicated space — an environment and a user — and hands it back. Within moments the panel lists enrolled nodes, ready to query.
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.
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.
OSCTRL
The core sense. Manage an osquery fleet through osctrl: list nodes, run queries, watch the endpoints. A small, token-authenticated plugin that ships against any osctrl.
NETDEVICE
Facts, interfaces, BGP / ARP / LLDP from routers, switches, and firewalls.
AWS · Azure · GCP
Cloud inventory, deployment status, and native posture findings — Security Hub, Defender for Cloud, Security Command Center. Collect only; the graph is downstream.
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 osctrl and osquery; everything else is a sense you can add.
A direction, moving
Venapce is real and in development. It ships as one image — Go backend, Vue panel, Superset dashboards, nginx, one Postgres behind them. It's proof of a pattern: the first product where all the business logic lives in FloMorphic workflows and the product itself is only the view. It isn't a replacement for your scanners or your cloud's own security engine — it reads from them on purpose. It's the connective tissue.
Venapce · the security segment of Inflowenger, built the FloMorphic way. In development — dates and scope will shift.