Aethyr Research
Documentation

Deployment Guide

Deploy Aethyr in the environment that best fits your requirements. Choose from local, hybrid, or cloud deployment options.

Deployment Options

Local Mode

Full air-gapped deployment. Data never leaves your infrastructure.

  • Highest isolation
  • Complete data control
  • Works offline

Hybrid Mode

Local data with optional cloud inference. Best of both worlds.

  • Local data storage
  • Cloud model access
  • Flexible scaling

Cloud Mode

Fully managed cloud deployment. Minimal setup required.

  • Quick setup
  • Scales with your workload
  • Managed updates

How Deployment Works

Aethyr is deployed by our team, inside your environment: on-premises, in your private cloud, or fully air-gapped. There is no self-serve installer; every deployment is provisioned and validated with you.

What You Provide

  • Access to the target environment (VMs, private cloud account, or air-gapped hardware)
  • Infrastructure baseline, sized with you during scoping to your document volume and models
  • Credentials for the data sources in scope
deployment-plan
# Deployment phases - run together with your Aethyr team

Phase 1 - Scoping
  - Deployment mode chosen: on-prem, private cloud, or air-gapped
  - Infrastructure baseline sized to your workload
  - Data sources and access model agreed

Phase 2 - Provisioning
  - Platform deployed inside your environment
  - Post-quantum identity issued for every component
  - Data-source connectors configured and validated

Phase 3 - Go-live
  - Success criteria verified against the pilot plan
  - Handover, training, and support channels active

Environment Configuration

Your deployment is configured through environment variables, finalized with your team during onboarding. Representative values:

.env.production
# Core connection strings (keep all credentials in a secrets manager)
DATABASE_URL=<database-connection-string>
CACHE_URL=<cache-connection-string>

# Application secret (generate a strong random value; never commit)
APP_SECRET=<generate-with-openssl-rand>
APP_URL=https://your-instance.com

# Model provider credentials - set only the providers you use
ANTHROPIC_API_KEY=<your-api-key>

# Deployment mode, local/air-gapped inference, and additional provider
# and knowledge-store settings are configured with your team during onboarding.

Security Best Practice

Never commit .env files to version control. Use secrets management for production deployments.

Production Checklist

  • Enable HTTPS

    Configure SSL/TLS certificates. Use Let's Encrypt for free certificates.

  • Configure Backups

    Set up automated database backups and test restoration procedures.

  • Set Resource Limits

    Configure memory and CPU limits in your deployment environment.

  • Enable Logging

    Configure centralized logging for monitoring and debugging.

  • Set Up Monitoring

    Configure health checks and alerting for system availability.

PreviousSecurityNextConfiguration