---
icon: material/launch
---

The engine runs next to logs, wherever they are produced. Find the estate below and follow its path.

<div class="grid cards" markdown>

-   :material-kubernetes:{ .lg .middle } __Kubernetes__

    ---

    A sidecar in the forwarder pod, or a standalone DaemonSet alongside it.

    [:octicons-arrow-right-24: Receiver deploy](https://doc.log10x.com/apps/receiver/deploy/)

-   :material-server:{ .lg .middle } __VMs and bare metal__

    ---

    A process beside the forwarder, installed from a package or the single-line script.

    [:octicons-arrow-right-24: Install](https://doc.log10x.com/install/linux/)

-   :fontawesome-brands-aws:{ .lg .middle } __AWS Lambda__

    ---

    A Lambda extension paired with the function's OTel collector, over loopback.

    [:octicons-arrow-right-24: Extension launcher](https://doc.log10x.com/engine/launcher/extension/)

-   :material-cloud-outline:{ .lg .middle } __CloudWatch only__

    ---

    A subscription-filter Lambda that processes log groups before they ship.

    [:octicons-arrow-right-24: Lambda launcher](https://doc.log10x.com/engine/launcher/lambda/)

</div>

## :material-source-branch: Pick by where logs are produced

The question is not which cloud the account is in; it is what runs closest to the application.

| Estate | What the engine attaches to | Install path |
|---|---|---|
| Kubernetes, any distribution | Forwarder sidecar or standalone DaemonSet | [Receiver](https://doc.log10x.com/apps/receiver/deploy/) |
| VMs, bare metal, edge hosts | A process beside Fluent Bit, Fluentd, Filebeat, Logstash, Vector, or an OTel collector | [Install](https://doc.log10x.com/install/) |
| AWS Lambda with an OTel collector extension | A second extension in the execution environment | [Extension](https://doc.log10x.com/engine/launcher/extension/) |
| AWS Lambda without one, or CloudWatch log groups | A subscription-filter Lambda | [Lambda](https://doc.log10x.com/engine/launcher/lambda/) |
| Scheduled or event-driven batches | A cron job, or a trigger on object storage | [Job](https://doc.log10x.com/engine/launcher/job/), [Trigger](https://doc.log10x.com/engine/launcher/trigger/) |

Eight forwarders are supported on the sidecar path, six of them natively: Fluent Bit, Fluentd, Filebeat, Logstash, OTel Collector, and Vector.

## :material-server-network-outline: Other platforms

Container platforms that support sidecars run the engine the same way Kubernetes does, and the sidecar recipe applies unchanged. Verified on Azure Container Apps: the engine and collector run as peer containers in one app, consuming an Event Hub with the [Streams](streams.md) configuration. Google Cloud Run is the same shape.

Serverless platforms with no place to run a second process, such as Azure Functions on the Consumption plan, stream their logs to a hub instead and let one central engine consume it. See [Streams](streams.md).

If an estate is not listed, ask the [MCP](https://doc.log10x.com/apps/mcp/): `log10x_discover_env` probes what is actually running and `log10x_advise_install` returns a plan for it.

## :material-map-marker-question-outline: Not sure which applies

Install the [MCP server](https://doc.log10x.com/apps/mcp/install/) and ask it to scan. It reads the cluster, the AWS account, or the host, then names the estate and emits the matching plan, including the case where more than one applies.

## :material-launch: Every launcher

The 10x Engine uses an extensible launcher framework to run
[apps](https://doc.log10x.com/apps/) in dev, edge, and cloud environments.

<div class="grid cards" markdown>

-   :material-laptop:{ .lg .middle } __Dev/Test__

    ---

    Execute a 10x Engine locally on Nix, Win, or OSX for development and testing.

    [:octicons-arrow-right-24: Learn more](https://doc.log10x.com/engine/launcher/dev/)

-   :simple-quarkus:{ .lg .middle } __Function__

    ---

    Execute 10x Engines in orchestrated environments via REST.

    [:octicons-arrow-right-24: Learn more](https://doc.log10x.com/engine/launcher/function)

-   :material-clock-time-three-outline:{ .lg .middle } __Job__

    ---

    Schedule 10x Engine execution via Linux cron or k8s CronJob.

    [:octicons-arrow-right-24: Learn more](https://doc.log10x.com/engine/launcher/job)

-   :material-lightning-bolt-outline:{ .lg .middle } __Trigger__

    ---

    Execute the 10x Engine in response to environment events (e.g., S3 trigger).

    [:octicons-arrow-right-24: Learn more](https://doc.log10x.com/engine/launcher/trigger)

-   :fontawesome-regular-object-group:{ .lg .middle } __Sidecar__

    ---

    Run the 10x Engine as a log forwarder sidecar to process events at the edge.

    [:octicons-arrow-right-24: Learn more](https://doc.log10x.com/engine/launcher/sidecar)

-   :fontawesome-brands-aws:{ .lg .middle } __Lambda__

    ---

    Run the 10x Engine as an AWS Lambda to optimize CloudWatch Logs before Datadog.

    [:octicons-arrow-right-24: Learn more](https://doc.log10x.com/engine/launcher/lambda)

-   :material-puzzle-outline:{ .lg .middle } __Extension__

    ---

    Run the 10x Engine as a Lambda extension paired with the function's OTel collector.

    [:octicons-arrow-right-24: Learn more](https://doc.log10x.com/engine/launcher/extension)

</div>