Playground Launch Overview
Use this outline when announcing the Relay Playground sandbox (playground.rufid.run).
Positioning
- Audience: developers evaluating Relay, internal teams needing safe experimentation.
- Promise: isolated sandbox mirrors production APIs without exposing customer data.
- Call to action: "Request access" or "Launch playground" button leading to console onboarding.
Key Messages
- Safe experimentation — sandbox tenants with daily resets and constrained resources.
- Production alignment — same execution engine + telemetry pipeline as production (low cardinality).
- One-click reset — workspace reset nightly; manual reset available via support.
Feature Highlights
- Tenant-scoped function catalog and execution history
- Real-time metrics (latency, errors) powered by FN-056 telemetry
- Rate-limited environment to prevent abuse (Cloudflare WAF + API guards)
- CLI + console support (
relay playground login, console executions tab)
Launch Checklist
- Update docs (
operations/playground-runbook,deployment/PLAYGROUND_GUIDE) - Enable console navigation link pointing to Playground
- Activate Cloudflare domain + WAF rules
- Configure support channel (
playground-support@deployrelay.com) - Publish blog/announcement post (coordinate with PMM)
Metrics to Track
- Playground executions per day (tag
environment:playground) - Onboarding completion rate (console usage analytics)
- Support tickets related to sandbox misuse/issues
FAQ
Is the playground production-ready? — No; it's isolated for experimentation. Performance and capacity are intentionally limited.
What happens if I hit limits? — Requests may be throttled (HTTP 429). Contact support if you need higher limits.
Can I request new features? — Use the feedback form in the console or email playground-support@deployrelay.com.
Keep this outline updated with final launch assets and metrics.