Development
Managed Headless browser on your own cluster
A Chromium your apps drive over the DevTools Protocol, for scraping, screenshots, PDFs and end-to-end tests.
Created inside a project, beside the apps that use it. Each project gets its own instance, storage and credentials.
A recent addition. It installs today, and the console marks it as new until it has run on a customer's cluster.
01What it does
Headless browser, run for you
Chromium's headless shell on Anyport's own chart, kept current with each release.
Puppeteer, Playwright and chromedp connect to it as a remote browser with the URL a bound app receives, so the browser lives beside your app instead of inside its image. Use it for scraping, screenshots, PDF rendering and end-to-end tests.
Each open page takes roughly 100 to 300Mi, so the size decides how many your apps can keep open at once. The DevTools Protocol has no password, so the browser is reachable only from inside its project and cannot be published on a domain; it can load anything the project can reach.
02Options
What you choose
What the console asks when you create it, in the catalog's own numbers. Anything marked chosen once cannot change without creating a new instance.
- Sizes
- small 1Gi, medium 2Gi, large 4Gi of memory
- Storage
- None
- Version
- Current stable Chromium, updated with each Anyport release
- Pause
- Yes
03Binding
What your app receives
Bind it to an app and these arrive as environment variables. The values are generated once into a secret and reach the app from there, rather than as something you copy.
- BROWSER_HOST
- BROWSER_PORT
- BROWSER_URL
04Adding it
Add Headless browser to a project
The same four steps as every service in the catalog.
- 01Open a project and go to Services.
- 02Pick it from the catalog and choose its options. Only the size is required; everything else has a default.
- 03Create it. Anyport installs it into the project's namespace, generates its credentials into a secret there, and tracks its health.
- 04Bind it to an app. The connection details arrive as environment variables, and rotating the credential never means editing an app.