# seed.run

> AI-optimized mirror of seed.run containing 50 pages totalling 19,236 words of clean markdown content, structured data, and semantic HTML. Original source: https://seed.run/. Last updated: 2026-06-13T19:19:16.677Z.

Each page is available as HTML (with JSON-LD structured data) and Markdown (text-only, ideal for LLMs and RAG).

## Homepage

- [Are you building a Serverless Framework app on AWS? Here’s how Seed can make your life a lot easier.](/content/site-root.html): Deploy, manage, and monitor Serverless applications (499 words)

## Articles & Blog Posts

- [docs/adding-a-build-spec/index.html](/content/docs/adding-a-build-spec/index.html) (1 words)
- [How It Works](/content/docs/issues-and-alerts/index.html): Issues in Seed makes it very easy to monitor your Serverless app. Issues is a native, real-time Lambda monitoring and alerting service, that: (1,298 words)
- [Advantages](/content/docs/native-error-reporting/index.html): Issues can detect most Lambda failures automatically. But errors and exceptions (the ones you catch in your code) need to be manually reported. To do this, simply log the error to the console and it’ll get reported. We call this Native Error Reporting. (996 words)
- [Removing an App](/content/docs/deleting-resources/index.html): Seed gives you the option to delete an app, a stage, or a service and also to remove the deployed resources using a serverless remove command. (367 words)
- [Check the Git log for updates](/content/docs/incremental-service-deploys/index.html): A monorepo Serverless app is one where multiple Serverless services are in the same repo. This means that a commit will trigger a deployment to all the services in Seed. However, this can be a slow process if you are only trying to deploy a change to a single service. (1,259 words)
- [Post-Deploy Phases in Monorepo Deployments](/content/docs/adding-a-post-deploy-phase/index.html): With monorepo deployments, you often want to run your integration tests after all your services have been deployed. To do this, Seed allows you to configure a post-deploy phase. A post-deploy phase can include a set of commands that you want to run after all your services have been successfully deployed. (544 words)
- [Prerequisites](/content/docs/index.html): Documentation for using Seed to build and deploy Serverless apps (498 words)
- [Custom Domains](/content/docs/customizing-your-iam-policy/index.html): Seed manages the serverless project in your AWS account on behalf of the IAM role that you create. This means that you need to specify the permissions Serverless Framework needs to deploy your project. (538 words)
- [Adding a Custom Domain](/content/docs/configuring-custom-domains/index.html): Seed can help you configure a custom domain for any API endpoint in your app. (863 words)
- [Installation](/content/docs/deploying-with-the-seed-cli/index.html): In addition to deploying through Git or your CI, you can trigger a deployment using the Seed CLI. (311 words)
- [AWS IAM Credentials for Seed](/content/docs/adding-your-iam-credentials/index.html): Seed needs your AWS IAM credentials to deploy your project on your behalf to your AWS account. (438 words)
- [Adding Members](/content/docs/adding-organization-members/index.html): Once you have created your organization, you can get started by adding members to it. (570 words)
- [Monorepo](/content/docs/mono-repo-apps-in-seed/index.html): Serverless Framework applications are made up of multiple services. A service can be thought of as a project that is based on a single serverless.yml file. By default, Serverless Framework applications start with a serverless.yml in the project root. (495 words)
- [Auto-Retrying on Deploy](/content/docs/auto-retrying-serverless-errors/index.html): When using Serverless Framework to continually auto-deploy branches and PRs, you might tend to run into a few issues. These issues can happen intermittently but the CloudFormation deployment might fail, leaving your stack in an unusable state. Meaning that you’ll need to completely remove the service before trying again. (668 words)
- [Prerequisites](/content/docs/enabling-gitlab-self-managed/index.html): Seed can easily connect to your GitLab Self-Managed account. This allows you to add a fully-managed CI/CD pipeline for your Serverless apps hosted on GitLab Self-Managed. (237 words)
- [Seed GitHub Integration](/content/docs/github-integration/index.html): Seed integrates really well with GitHub. In this chapter we’ll look at the various points of integration. (400 words)
- [Setting the region for a stage](/content/docs/multi-region-deployments/index.html): Seed makes it easy to deploy your Serverless app to multiple regions. (268 words)
- [Notification Options](/content/docs/adding-build-notifications/index.html): Seed makes it easy to configure your stages with email, slack, and custom webhook notifications. Notifications are sent when a build is deployed to a stage. (383 words)
- [Enabling Incremental Deploys](/content/docs/incremental-lambda-deploys/index.html): To speed up Serverless deployments, Seed incrementally deploys the Lambda functions in your service. It does this by checking if the CloudFormation template or Serverless config has been changed. If it hasn’t, then it’ll look at the individual Lambda functions in the service and deploy only the ones that have been updated. It’ll deploy the Lambda functions concurrently and directly, without doing a CloudFormation update. (440 words)
- [Second Generation Machines](/content/docs/build-machine-types/index.html): Seed runs your builds inside a virtual machine and there are three different machine types that can be used. (448 words)
- [Add a Staging (or Pre-Production) Stage](/content/docs/editing-the-pipeline/index.html): By default, apps in Seed are configured with a development and production stage. In the Adding a Stage chapter we covered how to add other development stages. However, you might want to add another downstream stage. Or you might want to replace the production stage. Seed allows you to do this through the pipeline editor. In this chapter we’ll look at how to edit your pipeline on Seed. (321 words)
- [Audit Log in Seed](/content/docs/audit-logs-in-seed/index.html): An Audit Log is a complete log of all the events in your organization in Seed. It keeps track of the activity of all the members in your organization. And it also keeps track of events generated by the Seed build system and your Git provider (commits, branches, PRs, etc.). (458 words)
- [Prerequisites](/content/docs/enabling-github-enterprise/index.html): Seed can easily connect to your GitHub Enterprise account. This allows you to add a fully-managed CI/CD pipeline for your Serverless apps hosted on GitHub Enterprise. (269 words)
- [Manually Deploy a Stage](/content/docs/manually-deploying/index.html): You can trigger one-off deployments to any stage or service in Seed. This can be useful for example, when you want to test a hotfix branch in your staging environment. (247 words)
- [Serverless Framework Environment Variables](/content/docs/configuring-stage-variables/index.html): Serverless Framework lets you define Lambda environment variables in serverless.yml that can be accessed in your Node.js Lambda functions using the process.env object. In Seed, you can set up stage specific variables easily by referring to the stage names in your Seed project. (317 words)
- [IAM Credentials per Stage](/content/docs/iam-credentials-per-stage/index.html): While adding your project to Seed, you are required to add the IAM credentials that you are going to deploy with. Seed uses these credentials for deployments to all the different stages. But it is good practice to deploy your stages to separate AWS accounts (or organizations). For example; you can separate your production and dev environments by deploying to completely different AWS accounts. (308 words)
- [Enable Docker](/content/docs/docker-commands-in-your-builds/index.html): You can run Docker commands as a part of your build process by adding them to your build spec. However, Docker is not enabled by default. (193 words)
- [Deploying Individual Git Branches](/content/docs/adding-a-stage/index.html): Seed supports both branch based workflow and pull request based workflow. In this chapter let’s look at how to deploy individual Git branches to different stages. (402 words)
- [Integrating with Serverless Pro](/content/docs/integrating-with-serverless-pro/index.html): Serverless Pro offers some similar features to Seed, like deployments and viewing logs and metrics. However, most of our users just use Seed. But if you’d like to deploy using Seed while viewing logs or metrics on Serverless Pro, you’ll need to follow a couple of quick steps. (148 words)
- [Deploy Phases](/content/docs/configuring-deploy-phases/index.html): Seed supports monorepo Serverless Framework apps. By default, all the services in a monorepo app are deployed concurrently. This means that a new git commit triggers a deployment to all the services in the monorepo app at the same time. (319 words)
- [Advantages of CDK and SST on Seed](/content/docs/adding-a-cdk-app/index.html): Seed supports deploying AWS CDK apps with SST v2. SST makes it easy to build serverless apps by using CDK constructs to define your infrastructure. And you can use it alongside your Serverless Framework services. (415 words)
- [Changing the stage](/content/docs/deploy-badges/index.html): Seed generates deploy badges for each of the stages in your app. A deploy badge is a little image that reflects the deploy status of a given stage. (235 words)
- [Newly created services](/content/docs/adding-a-service/index.html): Seed supports monorepo Serverless applications. This means that you can have multiple Serverless Framework projects (services) in the same repo. (427 words)
- [Seed for Serverless Python Projects](/content/docs/adding-python-projects/index.html): Seed makes it really easy to deploy Serverless Python projects. We support: (176 words)
- [GitHub](/content/docs/connect-your-own-ci/index.html): Seed can optionally allow you to connect to your own CI (continuous integration) service. This can be useful for cases where you have a complex set of tests or checks that need to be run before your app can be deployed. Or if your Serverless app needs to be deployed as a part of your existing infrastructure. By default, Seed will deploy your app automatically on git push to a branch. But you can optionally tell Seed that you only want to deploy after your CI process has completed successfully. (328 words)
- [Generating an SSH Key](/content/docs/adding-an-organization-ssh-key/index.html): You can set a private SSH key that Seed will use for all the build processes in your organization. There are a couple of reasons why you might want to do this: (415 words)
- [Generating Trusted Builds](/content/docs/generating-trusted-builds/index.html): When Seed builds your SST or Serverless Framework application, it generates some build artifacts as a part of the build process. These artifacts are stored for later use. In this chapter we’ll look at them in a bit more detail. (236 words)
- [Integrating with JFrog](/content/docs/integrating-with-jfrog/index.html): To use JFrog Artifactory with the npm registry you just need to add the following to your build spec (seed.yml): (124 words)
- [Node.js](/content/docs/caching-dependencies/index.html): Seed automatically caches dependencies to speed up your builds. Currently dependency cache is available for Node.js projects. If you would like support for other runtimes, feel free to contact us. This speeds up your builds if you are using Node.js. But it also speeds up deployments for other runtimes that are using Serverless Framework plugins. (264 words)
- [Problem](/content/docs/cannot-find-my-repo/index.html): Problem (227 words)
- [Two-Factor Authentication in Seed](/content/docs/enabling-mandatory-two-factor-auth/index.html): Seed supports two-factor authentication. And organizations on Seed can make it mandatory for their members to have to enable two-factor authentication on their accounts. (133 words)
- [Organization Accounts](/content/docs/creating-an-organization/index.html): Organization accounts are a way to group the team members and apps that belong to an organization. By default, any app created in Seed is under your personal account/namespace. Creating organizations gives you the ability to do the following: (182 words)
- [Seed Support for Node.js Projects](/content/docs/adding-nodejs-projects/index.html): Seed provides first-class support for Node.js projects. We currently support: (149 words)
- [Using Maven](/content/docs/adding-java-projects/index.html): Seed gives you a zero-config way to deploy Serverless Java projects. We currently support: (185 words)
- [Using the Makefile](/content/docs/adding-go-projects/index.html): Seed gives you a zero-config way to deploy Serverless Go projects. We provide out-of-the-box support for the following ways to build your project: (242 words)
- [Cancelling Builds](/content/docs/cancelling-builds/index.html): There are cases when something might go wrong while running a build and you might want to manually stop or cancel it. Seed allows you to cancel a build while it is in progress. (131 words)
- [Using a build script](/content/docs/adding-dotnet-core-projects/index.html): Seed gives you a simple way to manage deployments for your .NET Core 2.1 & 3.1 projects. We provide out-of-the-box support for the following ways to build your projects: (169 words)
- [Seed](/content/docs/adding-ruby-projects/index.html): Seed gives you a simple way to deploy Serverless Ruby 2.5 & 2.7 projects. We provide out-of-the-box support for packages installed using Bundler. (85 words)
- [sitemap-xml.html](/content/sitemap-xml.html) (610 words)

## Resources

- [Full Page Index](/index.html): Browse all cached pages with rich metadata
- [About This Cache](/content/about.html): Methodology, technical details, and usage guidelines
- [XML Sitemap](/sitemap.xml): Machine-readable sitemap for crawler discovery
- [Robots.txt](/robots.txt): Crawler directives