WebsitePlatform Login

System Requirements

Hardware and software requirements for meinGPT deployment

System Requirements

This guide outlines the minimum and recommended system requirements for deploying meinGPT in your environment.

Platform Requirements

Minimum Requirements

Hardware:

  • CPU: 4 cores (x86_64 or ARM64)
  • RAM: 8 GB
  • Storage: 50 GB SSD
  • Network: 100 Mbps

Software:

  • OS: Ubuntu 20.04+ / RHEL 8+ / Windows Server 2019+
  • Docker: 20.10+
  • Docker Compose: 2.0+
  • PostgreSQL: 14+ (with pgvector extension)
  • Node.js: 20+ (for development)

Hardware:

  • CPU: 8+ cores
  • RAM: 16-32 GB
  • Storage: 200 GB SSD (NVMe preferred)
  • Network: 1 Gbps

Software:

  • OS: Ubuntu 22.04 LTS
  • Kubernetes: 1.25+ (for production)
  • PostgreSQL: 15+ (with pgvector)
  • Redis: 7+ (for caching)

Enterprise Requirements

Hardware:

  • CPU: 16+ cores (dedicated)
  • RAM: 64+ GB
  • Storage: 1 TB+ NVMe SSD
  • Network: 10 Gbps
  • Load Balancer: Hardware or cloud-based

Software:

  • Kubernetes cluster (3+ nodes)
  • PostgreSQL cluster (primary + replicas)
  • Redis Sentinel/Cluster
  • Monitoring stack (Prometheus, Grafana)
  • Log aggregation (ELK or similar)

DataVault Requirements

Minimum Requirements

Hardware:

  • CPU: 4 cores
  • RAM: 16 GB
  • Storage: 100 GB SSD
  • GPU: Optional (for local embeddings)

Software:

  • Python: 3.10+
  • Weaviate: 1.23+
  • Docker: 20.10+

Hardware:

  • CPU: 8+ cores
  • RAM: 32-64 GB
  • Storage: 500 GB NVMe SSD
  • GPU: NVIDIA GPU with 8GB+ VRAM (for embeddings)

Software:

  • Python: 3.11+
  • Weaviate cluster
  • CUDA: 11.8+ (if using GPU)
  • Object storage (S3-compatible)

Enterprise Scale

For 1M+ documents:

  • CPU: 32+ cores
  • RAM: 128+ GB
  • Storage: 2+ TB NVMe
  • GPU: Multiple GPUs or GPU cluster
  • Dedicated vector database nodes

Network Requirements

Bandwidth

Minimum:

  • Upload: 10 Mbps
  • Download: 50 Mbps
  • Latency: Less than 100ms to AI providers

Recommended:

  • Upload: 100 Mbps
  • Download: 500 Mbps
  • Latency: Less than 50ms to AI providers

Ports

Required Ports:

  • 80/443: Web interface (HTTP/HTTPS)
  • 5432: PostgreSQL
  • 6379: Redis
  • 8080: Weaviate
  • 8000: DataVault API

Optional Ports:

  • 9090: Prometheus
  • 3000: Grafana
  • 5601: Kibana
  • 9200: Elasticsearch

Firewall Rules

Inbound:

  • HTTPS (443) from users
  • SSH (22) from admin network
  • Database ports from app servers

Outbound:

  • HTTPS (443) to AI providers
  • HTTPS (443) to authentication providers
  • NTP (123) for time sync
  • DNS (53) for name resolution

Browser Requirements

Supported Browsers

Desktop:

  • Chrome 100+ (recommended)
  • Firefox 100+
  • Safari 15+
  • Edge 100+

Mobile:

  • Chrome Mobile (iOS/Android)
  • Safari Mobile (iOS)
  • Samsung Internet

Browser Features

Required:

  • JavaScript enabled
  • Cookies enabled
  • WebSocket support
  • Local storage

Recommended:

  • Hardware acceleration
  • Ad blocker disabled for app domain

AI Provider Requirements

API Access

Required (at least one):

  • OpenAI API key
  • Anthropic API key
  • Azure OpenAI endpoint
  • AWS Bedrock access

Optional:

  • Google AI (Gemini) API
  • Mistral AI API
  • Cohere API
  • Groq API

Rate Limits

Minimum:

  • 60 requests/minute
  • 10,000 tokens/minute

Recommended:

  • 3,000+ requests/minute
  • 1M+ tokens/minute
  • Multiple API keys for load balancing

Storage Requirements

Database Storage

Growth Estimates:

  • User data: ~1 MB per user
  • Chat history: ~10 MB per 1,000 messages
  • Embeddings: ~4 KB per document
  • Metadata: ~1 KB per document

File Storage

Documents:

  • PDFs: Original + processed version
  • Office files: Converted to text
  • Images: Original + thumbnails

Backup Storage:

  • 3x production data for backups
  • Retention: 30 days minimum
  • External backup location recommended

Scaling Considerations

Vertical Scaling

CPU-intensive tasks:

  • Document processing
  • Embedding generation
  • PDF parsing

Memory-intensive tasks:

  • Vector search
  • Large language models
  • Caching

Horizontal Scaling

Application layer:

  • Stateless design
  • Load balancer required
  • Session sharing via Redis

Database layer:

  • Read replicas for scaling
  • Connection pooling
  • Query optimization

Monitoring Requirements

Metrics

System:

  • CPU utilization
  • Memory usage
  • Disk I/O
  • Network traffic

Application:

  • Response times
  • Error rates
  • Active users
  • API calls

Logging

Log retention:

  • Application logs: 30 days
  • Access logs: 90 days
  • Error logs: 180 days
  • Audit logs: 365 days

Backup Requirements

Backup Strategy

Daily:

  • Database backup
  • Configuration backup
  • User uploads

Weekly:

  • Full system backup
  • Vector database export

Monthly:

  • Archive old data
  • Test restore process

Recovery Objectives

  • RTO (Recovery Time Objective): Less than 4 hours
  • RPO (Recovery Point Objective): Less than 24 hours

Security Requirements

Encryption

In transit:

  • TLS 1.2 minimum
  • TLS 1.3 recommended
  • Strong cipher suites

At rest:

  • Database encryption
  • Encrypted backups
  • Encrypted file systems

Access Control

  • Multi-factor authentication
  • Role-based access control
  • API key management
  • IP whitelisting

Compliance Requirements

GDPR

  • Data residency in EU
  • Encryption requirements
  • Audit logging
  • Data deletion capabilities

ISO 27001

  • Documented processes
  • Regular audits
  • Incident management
  • Business continuity

Next Steps

  1. Review requirements against your infrastructure
  2. Plan capacity based on user count
  3. Set up monitoring before deployment
  4. Configure backups and disaster recovery
  5. Follow the deployment guide