The Cloud Sandboxes card on the Sandboxes page shows "$0.07 per user/month" in the monthly view and "$9 per user/month" in the annual view, while the same page says compute is "metered by the second" with "no recurring subscription fee" and $0.07 is really the Micro rate per hour. A developer reading the card cannot tell what they will pay, right where the new Lifecycle and GTM Analytics hires need clean signup data. Its credit button also reuses the Docker Pro button's tracking id, so those clicks can be counted as Pro plan interest.
First action
Rewrite the card copy and rename the two button ids.
How to measure it
Sandboxes page to credit-claim conversion
- Now
- –
- Target
- +20%
- By
- 60 days
Steps
Agree the copy
One price line, the per-second billing note and the free paused state.
Principal Product Manager, Sandboxes 1 day
Edit the card
Remove the monthly/annual toggle for Cloud Sandboxes.
Web team 1 day
Rename ids
Unique ids for the credit and AI Governance buttons.
Web team 2 hours
Re-check the Pro numbers
Split past "Pro" clicks by page.
Senior Marketing GTM Analytics Manager 2 days
Add an estimator link
Point to the size table and "what $250 buys".
Web team 1 day
Watch the funnel
Card views, credit claims and first cloud runs.
Senior Marketing GTM Analytics Manager weekly
Why it works
Replace the toggle-driven price with one honest line ("from $0.07 an hour, billed by the second; a paused sandbox costs nothing"), drop the monthly/annual toggle for this card, link the size table right under it, and give the credit and AI Governance buttons their own ids (for example dkr_pp_card_cloud_sbx and dkr_pp_card_aig). Then check last month's Pro click numbers for inflation from the Sandboxes page.
Usage pricing that reads like a seat price raises doubt at the moment of signup, and separate ids give the PLG team a true count of Cloud Sandboxes intent.
Ready to use
ChecklistCloud Sandboxes card fix
[ ] One price line: from $0.07/hour, billed per second [ ] Toggle removed for this card [ ] Link to the size table [ ] Credit button id renamed [ ] AI Governance button id renamed [ ] Old id mapped in the tag manager for 30 days [ ] Pro click history split by page
Risks and how to handle them
Dashboards built on the old id break
Map the old id to the new ones in the tag manager for a month.
Hourly price looks expensive at XL sizes
Lead with the Micro rate and the paused-costs-nothing line.
Evidence
- Your websiteDocker Sandboxes page, Cloud Sandboxes card: under the page's monthly/annual toggle the price reads "$0.07 per user/month" (monthly) or "$9 per user/month" (annual). The same page says "Cloud compute is metered by the second", "Pay-as-you-go, with no recurring subscription fee", and lists sizes per hour: Micro $0.07, Small $0.14, Medium $0.28, Large $0.56, XL $1.12. Checked October 22, 2026.Source
- Your websitePage source: both "Claim my $250 credit" buttons on the Cloud Sandboxes card, and both "Talk to an expert" buttons for AI Governance, carry the element id "dkr_pp_card_pro", the same id used by the Docker Pro "Buy now" buttons on /pricing (which link with refAction=wwwPricingProClicked).Source
- HiringSenior Lifecycle Marketing Manager (posted September 25, 2026): Docker's Product-Led Growth team "owns turning product usage into revenue" across the Container business and the AI business (Sandboxes, AI Governance, Model Runner, MCP Toolkit, MCP Catalog). Lifecycle already owns "user and admin nurtures, renewal automation, and first-touch outreach for PQLs and inbound leads" against "a marketable base in the tens of millions"; the hire must validate "an audience and its underlying signal before it ships".Source
- HiringSenior Marketing GTM Analytics Manager (posted September 3, 2026): owns "lead and account funnel analytics", "trusted attribution and return on investment methodologies" for marketing development funds, co-marketing and SPIFFs, "the targeting and measurement model for an inside sales motion into product led growth prospects", account scoring for ABM and new product adoption, and experiments that decide which programs "should scale, change, or stop".Source