New: LLM Rankings are live!

See how the top LLMs rank on real infrastructure tasks

Building Agentic Software Factories on AWS for Citizen Developers

Anyone on your team can build an app with a coding agent now. Getting that app onto real infrastructure is where it stalls. Watch this free workshop to set up a software factory in your own AWS account where the agent requests infrastructure and Massdriver deploys it, so the agent never holds AWS credentials.

Watch the Workshop

Recorded live on October 28, 2026. The November 4 session covered the same material.

Wednesday, October 28, 2026 · 9:00 AM PT

Watch the Recording

Speakers

  • Cory O'Daniel, CEO and Co-Founder, Massdriver

Why Agent Deployments Stall

Cloud Credentials

The usual options are giving the agent cloud credentials or putting the app in the platform team ticket queue.

Model Provider Exposure

If the agent uses a hosted model, your code and prompts go to a model provider outside your cloud account.

The Factory Fix

Every change the agent makes goes through Massdriver, is checked against your policies, and is limited to dev. Apps are built from infrastructure your platform team already approved.

Open-Weight Model on Bedrock

The model runs on Amazon Bedrock and is called from your own AWS account, so code and prompts stay under your AWS agreement.

What You Will Build From a Massdriver Canvas

Open-Weight Model

gpt-oss-20b on Amazon Bedrock that only your sandbox can call.

Locked-Down Sandbox

A VM sandbox running the opencode coding agent, wired to that model.

App Platform

A VPC, ECR, and a GitHub repo that builds on push, plus DynamoDB, S3, and Lambda behind an HTTP API.

Agent-Provisioned Infrastructure

Write an app with the agent in the sandbox, push it, and have the agent set up the infrastructure through the Massdriver Context Engine.

Before the Workshop: Set Up Your Accounts

Allow about 40 minutes, plus one optional request that can take a few days. You need an up-to-date browser and an AWS account you can sign in to as an administrator, with a payment method on file. Everything you build runs in your own AWS account, costs about $3, and is torn down at the end.

1. Create a Massdriver Account

About 5 minutes. Sign up at app.massdriver.cloud (it is free), create an organization with any name, and note your organization ID: the short name in the address bar after /orgs/.

Create free trial Massdriver account

2. Create an AWS Role for Massdriver

About 10 minutes. Make up a long External ID (running uuidgen works), then in the AWS IAM console create a role for another AWS account using Massdriver account ID 308878630280. Require the External ID, attach AdministratorAccess, name the role massdriver, and copy its ARN. You connect the role to Massdriver during the workshop.

3. Create a GitHub Organization

About 3 minutes. GitHub only lets an app create repositories inside an organization, so create a free one under Settings, Organizations, New organization. Note the organization login from its URL.

4. Create a GitHub App for Massdriver

About 15 minutes. In your new organization, open Developer settings, GitHub Apps, New GitHub App. Leave the callback URL empty and turn webhooks off. Repository permissions set to Read & write: Actions, Administration, Contents, Issues, Pull requests, Secrets, Variables, and Workflows (Metadata is Read-only). Organization permission: Self-hosted runners, Read & write. Install the app on All repositories, then note the App ID and Installation ID and download a private key (.pem).

5. Optional: Request GPU Capacity

About 5 minutes to request, and approval can take a few days. Only needed to run an open model on your own GPU. In US East (N. Virginia), open Service Quotas for Amazon EC2 and request 4 for Running On-Demand G and VT instances if yours is lower. Without it you skip the own-GPU part.

6. Optional: Install Terminal Tools

About 5 minutes. The whole workshop works in the browser. To use your own terminal or VS Code on the sandbox, install the AWS CLI and the AWS Session Manager plugin.

Bring These Values

Massdriver organization ID, AWS role ARN, External ID, GitHub organization login, GitHub App ID, Installation ID, and the GitHub App private key. Treat the External ID and the .pem file like passwords: do not email them, paste them into chat, or commit them to a repository.

Who It Is For

Platform engineers who get asked whether agents can deploy, and developers who want to ship an app without filing a ticket. No Terraform experience needed.

Watch the Workshop

Free, hands-on, and on demand. No Terraform experience needed.