CoderHelm Docs
Self-hosting

Everything you can set up

Every setting of a self-hosted install, where to set it (the install guide, the Launch Stack, the dashboard or the config), and how it is checked.

{/* Imported from CoderHelm/coderhelm-platform/docs/self-host/options.md at a9906dd2234a. Edit it there. */} One list of everything you can set up, and where. Required items are steps in the install guide; optional ones are in its Optional setup list after Ready, and in Settings, then Setup in the dashboard, each with a check and a fix.

At install

SettingRequiredInstall guideLaunch Stack parameterConfigChecked by
Your email (the first admin)YesYour emailAdminEmailadminsadmin
AWS regionYesAWS regionthe console's regionregion
Install nameMore optionsStagestage
Models: Bedrock or Anthropic keysMore optionsModelProvidermodels.providermodels, model
Bedrock inference profileBedrockInferencePrefixmodels.bedrockInferencePrefixmodel
Your own domainMore options, then the Domain stepHostname (HostedZone to pick a zone)domaindomain
Send email fromMore optionsEmailFromemail.from, email.identityemail, email_identity
Who else may sign upMore optionsSignupDomainsignup.domains, signup.emails
Automatic updates and the windowMore optionsAutoUpdate, UpdateWindow, UpdateTimezoneupdates.*updates
Anonymous install pingsTelemetrytelemetry.enabled
The release(the newest)Version--version
GitHub AppYesThe GitHub stepgithub-appgithub_app, github_installed, github_*
Claude access in BedrockYes, with BedrockThe Models stepmodels, model

After install

SettingWhereChecked byGuide
Your own domain, or change itSettings, then System, DomaindomainDomains
Email reaches anyone (leave the SES sandbox)The SES consoleemail_sandboxEmail
Email from your domain, with DKIMThe SES console, and DNSemail_identityEmail
Sign-up and password emails through SESemail.cognitoUsesSesEmail
Sign in with GoogleGoogle Cloud, the secret, integrations.googleSignIngoogle_sign_inSign-in and people
Invite your teamSettings, PeopleSign-in and people
Anthropic API key (Anthropic provider)Settings, AI models (per team)modelModel providers
Models a team usesSettings, AI modelsmodelModel providers
Repositories CoderHelm works onSettings, Repositories
Slack or Teams notices and alert routesSettings, Alertsslack, teamsIntegrations
JiraSettings, Integrations, JirajiraIntegrations
Connected AWS accounts (logs, metrics)Settings, Integrations, AWSIntegrations
Knowledge sources (Notion, Confluence, Google Drive and more)Settings, Knowledge; OAuth apps in the secretKnowledge sources
Automatic updates, channel, window, majorsSettings, SystemupdatesUpdates
Update notices in Slack or Teamsupdates.webhookUrlUpdates
BackupsOn by the install (point-in-time recovery on every table, versioned bucket); on-demand with backup; AWS Backup plansBackups
Keep data when stacks are deletedretainData (on)Config reference
The build sandbox, log analysis, weekly summaryintegrations.*Integrations
Support access for install adminsSettings, Support access (per team)Sign-in and people

Not available yet

  • Single sign-on (SAML or OIDC): sign-in is email and password (with passkeys and two-factor codes) or Google.
  • A private network (VPC): the functions run without a VPC and reach GitHub, Anthropic and Bedrock over HTTPS.
  • GitHub Enterprise Server: CoderHelm calls api.github.com.
  • Instance sizes: everything is serverless and pay per use; there is no size to pick. Model calls are most of the bill.
Edit on GitHub

On this page