Categories
Category strings (SOC2, HIPAA, EU) are accepted on routing today. They select a fixed runner pool and run with fallback inside that list. They are not a substitute for your own compliance review — Banana Peel does not attest that a completed run meets SOC 2 / HIPAA / EU residency requirements.
Current pools
SOC2— browserbase → steel → hyperbrowser → deckHIPAA— browserbase → steelEU— steel → hyperbrowser → browserbase
Successful creates echo a routing_note like category SOC2 — MVP routes within the configured pool; policy enforcement expands later.
When to use something else
If you don't have a compliance-shaped constraint, prefer routing: smart or an explicit runner chain — and pin a named runner (e.g. browserbase, skyvern) when you need to know exactly where the run executes. See Smart routing.