---
icon: material/cube-outline
title: "Product shape"
description: "What 10x is as a vendor relationship: licensed software the customer runs, with no log10x component in the path an event travels."
---

# Product shape

The questions a review opens with: what the software is, where it runs, and
where log content ends up.

| Property | Value |
|----------|-------|
| Engine version | **1.1.74** |
| Verified against | the shipped 1.1.74 release and images |
| Verified | 2026-09-01 |

## :material-help-circle-outline: The answers

| Question | Answer |
|----------|--------|
| What is the product | Licensed software the customer installs and runs |
| Where does it run | A Kubernetes DaemonSet, a sidecar, or an AWS Lambda layer, inside infrastructure the customer controls |
| Where does log content go | It stays where it already is and is forwarded to the customer's own SIEM |
| Does log content reach log10x | No, in every deployment mode |
| Does log10x run a production service in the data path | No |
| Vendor type | Software licensor |
| Data processor | No |

The engine reads events in place and writes them onward. There is no
log10x-side component in the path an event travels, which is why a review of
10x is a review of [what a deployed engine sends about itself](outbound.md)
rather than of a hosted service.

## :material-arrow-right-circle-outline: Next

| Page | What is on it |
|------|---------------|
| [Outbound](outbound.md) | The two calls a licensed deployment can make, and the states that remove them |
| [Deployment FAQ](../faq/security/deployment.md) | The deployment models in question form, including air-gapped estates |