Own the stack. Know the work.
Plan worker limits, access controls, secrets, job states, and recovery before deploying your own extraction runtime.
Journal collection
Deployment.
Your infrastructure. Your operating responsibilities.
Focused reading from the Extraction Journal. Start with the guide that matches the next decision in your workflow.
1 COMPLETE ARTICLERunning extraction on infrastructure you control creates choices about isolation, updates, credentials, storage, and recovery. This collection begins with a detailed self-hosting guide and connects to the AWS and Azure planning pages. It is an architecture resource rather than a packaged server or a container registry. Use it to evaluate software you have independently selected and verified. Start with a narrow workload and test resource limits, destination failures, and credential revocation before expanding access. A deployment is useful when it can explain job outcomes and recover without losing or duplicating records, not merely when a worker process stays alive.