BMC is the fully managed cloud instance of Estela. Deploy your first scraper in minutes — pay only for what you run. No DevOps, no infrastructure headaches.
No Kubernetes cluster, no DevOps engineer, no configuration. Create your account, push your scraper, and it runs.
Bandwidth, processing time, storage — every cost is itemized and visible. No black-box subscriptions, no surprises at month-end.
Bitmaker has been building web data infrastructure since before most scraping tools existed. That experience runs under every BMC deployment.
No infrastructure knowledge required. If you can write a spider, BMC handles everything else.
Sign up at cloud.bitmaker.dev. You get $5 in free credits automatically — no credit card needed. Your dashboard is ready immediately.
Run pip install estela-cli then authenticate with estela login. Your credentials are your BMC account — no separate setup required.
Run estela init in your existing Scrapy project root. This links your local project to BMC and generates the estela.yaml config. No code changes needed.
Run estela deploy. BMC containerizes your code automatically and allocates resources on demand. Your spider appears in the dashboard instantly.
Set a cron schedule, trigger via API, or run manually from the dashboard. Your scraper executes exactly when you need it to — no extra configuration.
Live logs, execution metrics, and itemized cost breakdown per scraper. Download extracted data as CSV directly from the Items tab — no extra tooling needed.
Pay only for the resources your scrapers actually consume. Every cost is visible in your dashboard in real time.
Charged per actual resource consumption. No idle fees, no seat-based pricing.
| Bandwidth | $1.00 / GB |
| Processing time | $0.0020 / min |
| Data retention | $2.00 / GB / month |
No subscriptions, no idle costs. Pay only when your scrapers run — every dollar visible in the billing dashboard.
✦ $5 in free credits to start
✦ Add a card only when you're ready to scale
Run Estela on your own infrastructure. Bitmaker handles installation, maintenance, and SLA-backed incident response — Standard, Professional & Enterprise tiers.
Everything engineering teams ask before deploying to BMC.
estela deploy from the project root — no rewrite, no custom decorators, no SDK lock-in. If your scrapers are based on requests (or httpx, Playwright, plain Python), they also run on BMC with only a few changes: wrap your entrypoint with estela-requests-wrapper so items, logs and stats flow into the dashboard the same way Scrapy spiders do.estela-requests-wrapper and estela-requests-entrypoint: thin adapters for plain requests, httpx, Playwright, or Selenium. The rule is simple: if you can put your scraper in a Docker image with a Python entrypoint, BMC can run it.pip install estela-cli, estela login, estela init in your existing Scrapy project, then estela deploy.pipelines.py, settings.py and middlewares keep working untouched. The only project-level addition is an estela.yaml (auto-generated by estela init) that declares which spiders to expose.estela create cronjob). Each schedule can target a specific spider with its own arguments and concurrency limits.We have a technical team specializing in custom web scraping — building new spiders from scratch or maintaining existing ones so they keep working reliably as target sites evolve.
Contact an Engineer →Full proactive supervision, dedicated TAM, 30-minute P1 response 24/7, monthly health reports, and a direct Slack line to Bitmaker's engineering team.
Contact for Enterprise →