Skip to main content
  • Keys
    OverviewDocumentationDashboardPricingUse cases
  • Testing
    OverviewDocumentationTesting dashboard
  • Integrations
  • Developers
    API portalGitHub
Sign in
Keys OverviewDocumentationDashboardPricingUse cases Testing OverviewDocumentationTesting dashboard Integrations Overview Developers API portalGitHub
Sign in
Testing

Start

Docs homeWalkthroughOverviewHow it fits together

Getting started

New projectExisting stack

Guides

CI / GitHub ActionsFork PRs & triggersHTTP runs vs ActionPerformance goalsConfigurationTest definitionPlot dogfoodingKeys in CI (checklist)Keys + Testing (dashboard)

Integrations

Restormel Keys

Reference

ArchitectureCompatibilityExamples
Docs homeTesting hubSign in
Testing/ Docs/ journeys/ keys
Using Restormel Keys? Canonical setup for hosted credentials + CI env: Keys + Testing onboarding · Dashboard hub: Restormel Testing · Agents: MCP tools testing.journey, testing.ci_env_template, testing.resolve_probe.

Journey: BYOK through Keys

You want test runs to respect the same resolve and policy story as production.

Read Keys integration for Testing-specific process env (RESTORMEL_KEYS_*, fallback), then Walkthrough — Phase 2 — Wire Keys. For dashboard setup (Connections, Restormel Testing hub, RESTORMEL_PROJECT_ID): Keys + Testing onboarding. Keys dashboard and resolve API detail: Keys docs.

Keys
  • Restormel home
  • Overview
  • Documentation
  • Dashboard
  • Pricing
  • Use cases
Testing
  • Overview
  • Documentation
  • Testing dashboard
Integrations
  • Overview
Developers
  • API portal
  • GitHub
Legal & resources
  • Terms
  • Privacy
  • Refund policy
Restormel

Keys, Testing, and integrations for production AI teams

restormel.dev