Quick start

You can have your first app live in about ten minutes. Here is the short version.

1. Create an account. Head to the signup page and create an account. Free, no card needed.
2. Create a project. Either connect a GitHub repository, or drag and drop a ZIP file with your code.
3. Pick a region and a profile. Eigon suggests a region based on where you are. The Free profile is great for experiments. Production turns on WAF, CloudFront and other safety nets.
4. Click Deploy. Eigon detects the framework, builds an image, provisions the AWS infrastructure, and brings the service online. You will see a live progress rail explaining every step.
5. Open the URL. You get a real HTTPS URL the moment the service passes its health check. Add a custom domain whenever you are ready.

Core concepts

Three things to keep in mind. Everything else builds on these.

• Project. A single app, tied to one source (GitHub repository or uploaded ZIP). A project has a name, a framework, and a set of environments.
• Environment. A live copy of your app running on AWS. Most projects have a couple, for example dev and prod. Each environment has its own variables, domain, region, spending cap, and deployment history.
• Deployment. An immutable snapshot of your code plus configuration that has been built, pushed and rolled out to an environment. Every deployment is logged and rollback is one click.

Connecting your code

Eigon supports two source types. A project always has exactly one of them.

GitHub

Connect your GitHub account once. Pick the repository and the default branch. Every push to that branch can either deploy automatically (auto deploy on) or wait for you to click deploy in the dashboard.

ZIP upload

No GitHub account required. Drag and drop a ZIP of your project into the upload modal. We store it in S3 with versioning, run the same build pipeline, and let you redeploy from the dashboard whenever you upload a new version.

You can switch a project between GitHub and ZIP at any time from the project settings page. The switch is atomic so there is never a moment where the project has both sources.

Environments and variables

Each environment has its own variables and secrets. Set them once in the dashboard and they get injected into your container at runtime.

• Plaintext variables are stored encrypted at rest and shown in the dashboard so you can edit them.
• Secrets live in AWS SSM Parameter Store with KMS encryption. Once you save them they are never shown again, only referenced.
• Bulk import from a .env file works for both. Paste it into the variables modal and we will parse it.

You can promote variables between environments from the variables page so dev and prod stay in sync without copy and paste.

Deploying your app

When you click Deploy, Eigon walks through these steps. The dashboard shows you exactly which step is running and what it is doing in plain English.

1. Analyze. Detect the framework, the language, and the build commands. If we are not sure, the AI fallback takes a look at your code structure to fill in the blanks.
2. Build. CodeBuild clones your repository (or unpacks the ZIP), builds a Docker image, and pushes it to ECR.
3. Plan. Eigon generates a CloudFormation template tailored to your framework, region and profile.
4. Provision. The template is applied. ECS, ALB, RDS, ElastiCache, CloudFront, WAF, IAM and so on come up in the right order.
5. Health check. Eigon waits for your app to respond on its health endpoint before marking the deploy as successful.

Every deployment is reversible. Click any previous successful deployment in the history and hit Rollback. The infrastructure stays the same, only the image switches.

Custom domains and SSL

Every environment ships with a free *.eigon.app URL on day one. Adding your own domain takes a minute.

1. Open Settings, Domains, Add domain on any environment.
2. Copy the CNAME record we show you and add it at your DNS provider (Cloudflare, Namecheap, Route 53, etc).
3. Click Verify. Once DNS propagates we request a certificate from AWS Certificate Manager. SSL is free and renews automatically.

Spending caps

This is the headline feature. Every environment has a hard monthly cost ceiling. The default depends on your plan and you can raise or lower it any time from the environment settings page.

We compare your month to date spend against the cap once an hour and trigger actions at four thresholds:

• 50 percent: a friendly heads up email.
• 80 percent: a warning email with a projection of when you will hit the cap.
• 95 percent: an urgent email plus a banner across your dashboard.
• 100 percent: graceful degradation. We scale your services to the minimum, disable autoscaling, and pause new deploys until you raise the cap or the next month rolls over.

You can choose between three actions at 100 percent: alert only, graceful degrade, or hard stop. Most users leave it on graceful degrade.

Logs, metrics, and Copilot

Logs and metrics are surfaced directly in the dashboard. Logs come from CloudWatch with a live tail option. Metrics come from CloudWatch and ALB telemetry, refreshed every five minutes.

Eigon Copilot is a chat panel on every environment page. It is grounded in your Project Brain, which means it can see your infra graph, your recent logs, your metrics, and your deployment history. Ask questions like "why is my app slow?" or "what changed in the last deploy?" and you will get an answer that cites real data, not made up suggestions.

The eigon CLI

Install the CLI on macOS or Linux:

curl -sSL https://eigon.io/install.sh | sh

Then create an API token at Account, Tokens and log in:

eigon login           # paste your token
eigon whoami          # confirm you are signed in
eigon projects list
eigon deploy --env env_xxx
eigon status --env env_xxx
eigon logs --env env_xxx --tail
eigon flags list --env env_xxx
eigon export-tf --env env_xxx --org org_xxx --project proj_xxx

You can also pass EIGON_TOKEN as an environment variable instead of running eigon login. That is the pattern most CI systems use.

GitHub Actions

Drop this workflow at .github/workflows/deploy.yml in your repository, then add an EIGON_TOKEN secret in your repository settings.

name: Deploy to Eigon
on:
  push:
    branches: [main]

jobs:
  deploy:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: ayushcodes10/eigon-cli/cli/github-action@v1
        with:
          token: ${{ secrets.EIGON_TOKEN }}
          environment: env_REPLACE_ME
          wait: true

The action installs the CLI, triggers the deploy, and waits for it to finish. If the environment hits its spending cap, the workflow fails with a clear error and a link back to your dashboard.

Slack, Discord, and webhooks

Get notified when a deploy succeeds or fails, when a spending cap threshold is crossed, or when an environment changes state. Set this up in Project, Settings, Integrations.

• Slack: paste an incoming webhook URL from your workspace. We post nicely formatted messages with action buttons.
• Discord: same pattern, paste a webhook URL from your channel settings.
• Generic webhook: any HTTPS endpoint. We send a JSON payload with an HMAC SHA256 signature so you can verify authenticity.

Feature flags

Eigon ships a small built in feature flag service. Flags live per environment and support deterministic rollout percentages.

Read flags from your app via a small HTTP call to /api/environments/<env_id>/flags, or inject them as environment variables on deploy. Flip them at any time from the dashboard or via the CLI:

eigon flags set new_checkout=true --env env_xxx

Exporting to Terraform

Click Export to Terraform on any environment and you get a zip file containing a ready to apply Terraform module. Network, ALB, ECS, RDS, Redis, CloudFront, WAF and outputs are all included.

You can run this Terraform directly against your own AWS account if you ever decide to leave Eigon. There is no lock in. We think this is the right way to earn long term trust.

Billing

You pay Eigon a flat platform fee for the control plane. Your AWS workloads run in your own AWS account or in Eigon Managed Cloud and the underlying AWS charges are billed at AWS list prices. See the pricing section on the home page for the current plan list.

Spending caps protect you no matter what plan you are on. If your environment hits its monthly cap, Eigon scales it down to a minimum footprint and pauses new deploys until you raise the cap or the next month rolls over.

Help and support

The fastest way to reach us is the live chat widget at the bottom right of the dashboard. For anything that does not need a real time reply, email info@eigon.io. We answer every message.

For status and incidents see the status page. For everything we have shipped and what is next, see the changelog.