Self-hosting

The Self-Hosted plan runs the same stack the hosted service runs, in your Azure subscription, under your governance. Setup is guided end to end from your Maester Cloud account: you never have to assemble the infrastructure yourself.

What you'll deploy

One resource group in the region you choose, containing the Maester Cloud web app and API, the Maester Cloud Runner, and Azure Storage for reports, results, history, queues, and supporting tables. Everything stays inside your subscription.

Prerequisites

• An active Maester Cloud subscription.
• An Azure subscription where you can create resource groups and assign roles. Setup signs you in to Azure directly, so no CLI is required.
• Permission to create an app registration in Microsoft Entra, or an identity team that creates the sign-in app for you. See portal sign-in.

Deploy

1. Sign in to your Maester Cloud account and start setup.
2. Sign in to Azure and Microsoft Graph when prompted, then pick the subscription, region, and name for your instance.
3. Follow the guided steps. Setup registers the sign-in app in your tenant, creates the resource group, and deploys the stack.

Setup is resumable: if you close the tab partway through, it picks up where you left off.

Custom domain

Your subscription includes up to three subdomains under a Maester-operated domain (like contoso.maester.fyi), or you can bring your own domain. The portal's Domains page lists every name registered to your account and the instance each one points to. Both run from setup's Custom domain step: it adds the address to your instance, requests a free certificate that renews automatically, and registers sign-in for the new address. The instance's original Azure address keeps working either way. Maester-provided subdomains are covered by the Terms of Service.

Onboard and run your first check

From here the experience matches hosted: sign in, follow the in-portal checklist, and connect your Microsoft Graph tenant. The built-in Maester Cloud Runner then runs your tests for you, and results land in the portal automatically.

You can also upload reports yourself from your own pipelines with Send-MaesterCloudReport from the MaesterCloud module, pointing -PortalUrl at your portal URL, once an Owner has ticked Uploader for you on the Access page. See Sending reports. To get run reports and regression alerts by email, set up drift emails.

Staying current

New releases are applied by re-running setup from your account, which updates your instance in place. Deployments are idempotent, and your data (the storage account) is untouched by stack updates. Release announcements go to subscribers by email.