Skip to main content
Setting up a Mjolnir run involves several steps — connecting repositories, configuring targets, adding test users, and uploading documentation. Drafts let you save your progress and come back to it later, or maintain multiple configurations for different applications.

​
Auto-saving

Odin automatically saves your setup progress as you work through the wizard. You don’t need to manually save — your current step, selected repositories, target URLs, test users, uploaded files, and all other configuration is preserved automatically. If you close the browser or navigate away mid-setup, your draft is waiting for you when you return.

​
Managing drafts

When you start a new Mjolnir run, any existing drafts are shown before the setup wizard. From here you can:
  • Resume a draft to continue where you left off
  • Rename a draft to give it a descriptive label (e.g. “API v2 staging” or “Mobile app production”)
  • Delete a draft you no longer need
If you test multiple applications with Mjolnir, use draft labels to keep track of which configuration belongs to which app. Each draft stores the full setup state independently.

​
What’s saved in a draft

A draft captures the entire setup wizard state:
  • GitHub connection and selected repositories
  • Target URLs and custom headers
  • Connectivity check results
  • Rate limiting configuration
  • Test user credentials
  • Code and documentation uploads
  • Domain verification status
  • Selected pricing tier
  • Current wizard step and progress
When you resume a draft, you’re returned to exactly where you left off with all configuration intact.

Start a Mjolnir run

Learn how to launch and monitor pentest runs