draft overview

Author: nicktrn

docs/self-hosting/overview.mdx

@@ -0,0 +1,67 @@
+---
+title: "Overview"
+description: "You can self-host Trigger.dev on your own infrastructure."
+tag: "v4"
+---
+
+Self-hosting Trigger.dev means you run and manage the platform on your own infrastructure, giving you full control over your environment, deployment process, and the URLs you expose the service on.
+
+You are responsible for provisioning resources, handling updates, and managing any security, scaling or reliability challenges that arise.
+
+We provide version-tagged releases for self-hosted deployments. It's highly advised to use these tags exclusively and keep them locked with your CLI version.
+
+## Should you self-host?
+
+For most users, Trigger.dev Cloud offers the best experience - it's fully managed, scalable, and comes with dedicated support. However, if you have specific requirements around data residency, compliance, or infrastructure control, self-hosting may be the right choice for you.
+
+The self-hosted version is functionally the same as Trigger.dev Cloud with [some exceptions](#feature-comparison), but our managed Cloud infrastructure is designed for high availability, security, and scale.
+
+Because we do not manage self-hosted instances, we cannot guarantee how Trigger.dev will perform on your infrastructure. You assume all responsibility and risk for your deployment, including security, uptime, and data integrity.
+
+You can read the rest of this overview and follow our guides for instructions on setting up a self-hosted Trigger.dev instance. If you prefer a managed experience, you can [sign up](https://cloud.trigger.dev/login) for our Cloud offering instead - we have a generous [free tier](https://trigger.dev/pricing) for you to try it out.
+
+{/* TODO: Architecture section with updated diagram */}
+
+## Feature comparison
+
+While [limits](#limits) are generally configurable when self-hosting, some features are only available on Trigger.dev Cloud:
+
+| Feature           | Cloud | Self-hosted | Description                             |
+| :---------------- | :---- | :---------- | :-------------------------------------- |
+| Warm starts       | ✅    | ❌          | Faster startups for consecutive runs    |
+| Auto-scaling      | ✅    | ❌          | No need for manual worker node scaling  |
+| Checkpoints       | ✅    | ❌          | Non-blocking waits, less resource usage |
+| Dedicated support | ✅    | ❌          | Direct access to our support team       |
+| Community support | ✅    | ✅          | Access to our Discord community         |
+| ARM support       | ✅    | ✅          | ARM-based deployments                   |
+
+
+## Limits
+
+Most of the [limits](/limits) are configurable when self-hosting, with some hardcoded exceptions. You can configure them via environment variables on the [webapp](/self-hosting/env/webapp) container.
+
+| Limit             | Configurable | Hardcoded value |
+| :---------------- | :----------- | :-------------- |
+| Concurrency       | ✅           | —               |
+| Rate limits       | ✅           | —               |
+| Queued tasks      | ✅           | —               |
+| Task payloads     | ✅           | —               |
+| Batch payloads    | ✅           | —               |
+| Task outputs      | ✅           | —               |
+| Batch size        | ✅           | —               |
+| Log size          | ✅           | —               |
+| Machines          | ✅           | —               |
+| Log retention     | —            | Never deleted   |
+| I/O packet length | ❌           | 128KB           |
+| Alerts            | ❌           | 100M            |
+| Schedules         | ❌           | 100M            |
+| Team members      | ❌           | 100M            |
+| Preview branches  | ❌           | 100M            |
+
+{/* TODO: Maybe clarify re OFFLOAD_IO_PACKET_LENGTH_LIMIT */}
+
+{/* TODO: add machine overrides section */}
+
+## Community support
+
+It's dangerous to go alone! Join the self-hosting channel on our [Discord server](https://discord.gg/NQTxt5NA7s).