Massdriver Platform Update: Thanksgiving 2026 Massdriver's Thanksgiving 2026 platform update adds LLM Rankings for real infrastructure tasks and lets customers move an instance between projects while preserving its configuration, secrets, IaC state, resources and deployment history. Massdriver is also deprecating service account secrets: after December 31, 2026, secrets no longer authenticate, and customers must replace them with access tokens prefixed `md_` that carry scopes and expiry dates and can be revoked individually. The release additionally adds signed webhook delivery of audit log events to customer-chosen HTTP endpoints, visibility into the environments external resources come from, a bundles drawer, and development releases for resource types. New: LLM Rankings are live See how the top LLMs rank on real infrastructure tasks https://www.massdriver.cloud/llm-rankings Move an instance to another project with its state and history, send audit log events to your own endpoints with filters and jq conditions, see where external resources come from and who can give you access, a bundles drawer that shows what the project can use, audit logs that record how each actor signed in, development releases for resource types, and the end of service account secrets on December 31. November added runtimes, OIDC credentials for deployments, and custom default tags. This release lets you move an instance into another project and keep its state, resources, and history. Massdriver can now send audit log events to an HTTP endpoint that you choose. This release also shows the environments that your external resources come from, and the groups to ask when you cannot see them. Replace each service account secret with an access token before December 31, 2026. After that date, service account secrets do not authenticate. Access tokens start with md , have scopes and an expiry date, and you can revoke one token without stopping the others. Each new service account gets an access token named "Default". Create more with createServiceAccountAccessToken . Send the access token everywhere you send the secret now: API requests curl -X POST https://api.massdriver.cloud/api/v2 \ -H "Content-Type: application/json" \ -H "Authorization: Bearer md xxxxxxxxxxxxxxxxxxxxxxxx" \ -d '{"query": "{ viewer { typename } }"}' Mass CLI export MASSDRIVER API KEY=md xxxxxxxxxxxxxxxxxxxxxxxx Terraform and OpenTofu state backend export TF HTTP USERNAME=your-org-identifier export TF HTTP PASSWORD=md xxxxxxxxxxxxxxxxxxxxxxxx Check CI pipelines, state backends, Mass CLI configuration files, and scripts that send Authorization: Bearer or the x-md-api-key header. Replace the x-md-api-key header with Authorization: Bearer md ... , where the value is the access token. The service account secrets deprecation https://docs.massdriver.cloud/deprecations/service-account-secrets page has the full migration checklist. Move an instance into another project. It keeps its configuration, secrets, IaC state, resources, and deployment history. Open the instance, then select Actions → Move to another project . Pick the destination environment and the component ID. The dialog shows the new instance ID before you move. For example, billing-prod-vpc moves to project network , environment prod , as component vpc , and becomes network-prod-vpc . The move keeps the instance's IaC state where it is, so nothing is copied and cloud resource names do not change. Massdriver does these steps in one transaction. If one step fails, nothing changes, and you get every problem in one list. preserveHistory: true in the API , its deployments, alarms, and costs move onto the moved instance. Cloud tags, cost data, and alarms keep the old identifier until the next deployment. After a move, the instance shows Moved from with its old ID until you deploy it. mutation { moveInstance organizationId: "acme" id: "billing-prod-vpc" environmentId: "network-prod" componentId: "vpc" input: { preserveHistory: true } { successful result { id status } messages { message } } } A move needs the new instance:move permission on the instance. The admin group has it. Other groups do not get it by default. A move also needs project:design when it adds a component, instance:configure and resource:view for each new remote reference, and resource:grant for each grant it adds. Send audit log events to your own HTTP endpoint as signed webhooks. An event destination receives the organization's audit log events that match its filter. Use one to start a pipeline when a deployment fails, send production changes to a SIEM, or post to a chat channel. Each request is one CloudEvent https://cloudevents.io in structured mode application/cloudevents+json . The CloudEvent id is the audit log event's ID, so your receiver can drop duplicates. The filter has four fields. An event must match every field that you set. An empty field matches every event. types : event types, or