Scrapyd, the service you deploy your Scrapy spiders to, so crawls are scheduled, queued and logged in one place instead of run by hand.
Scrapyd is an open source daemon for deploying and running Scrapy spiders. You package a Scrapy project as a Python egg and upload it, then start, queue, monitor and cancel crawls through a JSON HTTP API, so scheduling a spider becomes a single call rather than a session on a machine. It keeps several versions of a project side by side, runs a bounded number of spiders at once, and writes a separate log and a separate scraped items file for every job, all reachable from a small web console that lists what is pending, what is running and what has finished. Because the API is plain HTTP, crawls can be triggered from cron, a CI pipeline or your own application, and the same instance can hold many unrelated projects.
Upstream turns authentication off whenever its username or password is left unset, and the endpoint that accepts a project upload runs code from it, so an unauthenticated instance is far more than an open job queue. cloudimg never ships it that way. Each instance generates two separate credentials of its own on first boot: one for the front door that you use, and a different one that only the reverse proxy and the daemon share, so a project you deploy cannot read the credential you sign in with. Nothing usable is baked into the image, the daemon and its sample crawl target are bound to loopback with a single hardened front door in front, and the services refuse to start at all if a credential is missing rather than starting open. A bundled sample project and a catalogue served on loopback mean the first crawl works straight away and sends no traffic to anyone else's site. Every deployment ships fully patched, with a paired deploy guide and 24/7 cloudimg support.
Real screenshots taken while testing this image against its deployment guide.