Repository navigation
Replies: 2 comments
0 replies
|
For a weekly Browserbase-backed Stagehand job, GitHub Actions cron is usually the simplest production setup: checkout, install deps, run your Stagehand script, and keep Browserbase/model keys in Actions secrets. Browserbase is already hosting the browser session, so the scheduler only needs to run your Node process. I would move to Cloud Run + Cloud Scheduler when you need a pinned container image, private networking, longer/retried jobs, or better runtime observability. Vercel Cron is fine if the job is naturally an HTTP handler, but for a small scheduled browser automation script, Actions or Cloud Run is usually a cleaner fit. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi anyone👋
I’m exploring how to best run Stagehand in a production environment and I’m wondering what setup you recommend.
My goal is pretty simple:
I want to run a small Stagehand script
The script should execute automatically, e.g. once a week
I’m using Browserbase as the backend for Stagehand
Right now, I’m considering deploying the script via Google Cloud Run and triggering it with Cloud Scheduler, but I’m wondering if that’s overkill.
Is there an easier or more “official” approach you’d recommend for production? For example:
Using GitHub Actions with cron?
Deploying a lightweight serverless function (e.g. Vercel Cron Jobs)?
Or is Cloud Run the best way if I want something more robust?
I’d really appreciate your advice on the simplest and most reliable setup for this kind of job 🙏
Thanks!
All reactions