Development and demonstration applications hosted on AIC Holdings cloud infrastructure. Always-on services running 24/7/365 on enterprise-grade infrastructure.
Server 80.209.241.157
8 vCore | 32GB RAM
Demo Applications
?
About This Server Info
Learn about this server, why it exists, and what it's used for.
Live deployment status from Coolify container orchestration.
About This Server
This is an inexpensive, always-on cloud server providing 24/7/365 uptime for testing, development, and infrastructure operations.
Why This Server Exists
Local development machines sleep, restart, and go offline. This dedicated server provides:
24/7/365 Availability — Always online for scheduled tasks, webhooks, and integrations
Cost-Effective Testing — Inexpensive platform for testing deployments before production
MCP Gateway — Always-on Model Context Protocol server for AI agent connectivity
Multi-Tenant Hosting — Isolated environments for AIC Holdings and Jetta Operating
Server Specifications
Server ID
62022
IP Address
80.209.241.157
Provider
Hostkey
Operating System
Ubuntu 24.04 LTS
CPU
8 vCore
RAM
32GB
Location
Europe
Installed Runtimes
Python 3.12 with pip, Streamlit, and common libraries
Node.js v22 with npm
Claude Code CLI for AI-assisted development
Access Methods
Web Apps: Various ports (3000-3001, 8000-8501)
SSH: Standard SSH access for terminal
Remote Desktop: xRDP on port 3389
For questions or access requests, contact AIC Holdings.
MCP Gateway
This server is configured as an always-on MCP (Model Context Protocol) gateway, enabling AI agents to connect to tools and services 24/7.
What is MCP?
Model Context Protocol is an open standard that allows AI assistants like Claude to securely connect to external tools, databases, and APIs. An MCP gateway provides persistent connectivity that doesn't depend on a local machine being online.
Organizations Supported
AIC Holdings — Investment and holdings company operations
Jetta Operating — Operating company infrastructure
Gateway Capabilities
Persistent Connections — MCP servers run 24/7, no laptop required
Multi-Tenant — Isolated MCP configurations per organization
Remote Access — Connect from any Claude client via SSH tunneling
Planned MCP Integrations
M-Files
Document management and workflow
Wrike
Project management and task tracking
HubSpot
CRM, contacts, and deals
Sable
Banking and financial data
Meridian
Energy trading and operations
Supabase
Database operations for all projects
Custom APIs
Organization-specific integrations
Authentication
Employee Claude Code instances authenticate via API key. Each organization (AIC Holdings, Jetta Operating) has isolated credentials and access controls. API keys are managed centrally and can be revoked at any time.
Architecture
MCP servers run as background processes on this server. Claude clients connect via SSH tunnel or direct socket connection, enabling AI agents to perform operations even when the user's local machine is offline.
MCP Gateway setup in progress. Contact AIC Holdings for access.
CI/CD Pipeline
Automated continuous integration and deployment pipeline that syncs GitHub repositories directly to this server. Push to main, and the server updates automatically.
Why Automate Deployments?
Manual deployments are error-prone and slow. With CI/CD automation:
Zero Manual Steps — Push code, walk away, it's deployed
Instant Updates — Changes go live within seconds of merge
Rollback Support — Easy revert to previous versions if needed
Audit Trail — Every deployment linked to a specific commit
How It Works
1. Push to GitHub
Developer pushes code to main branch
2. Webhook Fires
GitHub sends POST to server webhook endpoint
3. Server Pulls
Server runs git pull on the repository
4. Build & Restart
Dependencies installed, services restarted
5. Health Check
Verify app is running correctly
Repositories to Connect
hostkey-server — This server's configuration and demo apps
Jetta project repos — Operating company applications
Implementation Options
GitHub Actions
SSH into server and run deploy script
Webhook Listener
Node.js/Python service listening for GitHub webhooks
Watchtower
For Docker containers, auto-pull new images
systemd Timers
Periodic git pull as fallback
Security Considerations
Webhook Secret — Verify requests actually come from GitHub
Deploy Keys — Read-only SSH keys for each repository
Branch Protection — Only deploy from protected main branch
Secrets Management — Environment variables stored securely, not in repo
Planned Architecture
A lightweight webhook listener will run on this server, validating GitHub signatures and executing deploy scripts per-repository. Each app has its own deploy script handling build steps and service restarts.
CI/CD pipeline setup in progress. Target: automatic deploys for all demo apps.
Security & Access
This page explains how we keep this server secure and how authorized team members can get access. No advanced technical knowledge required.
Who Can Access This Server?
Only authorized employees of AIC Holdings and Jetta Operating can access this server. Access is granted on an as-needed basis by the IT administrator.
How to Get Access (For Employees)
If you need access to this server, here's what to do:
Request Access — Contact your manager or IT administrator
Get Your Key — IT will provide you with a secure "SSH key" (think of it like a special password file)
Save Your Key — Store it in a specific folder on your computer (IT will help)
Connect — Use the provided connection instructions
The key file is like a digital ID badge — only your computer has it, and the server recognizes it.
What About Passwords?
We don't use passwords for server access. Why? Because:
Passwords can be guessed or stolen
SSH keys are mathematically impossible to crack
Keys can be instantly revoked if someone leaves the company
Types of Access
Web Apps
Anyone can view (public demos)
Terminal (SSH)
Authorized users with SSH keys only
Remote Desktop
Authorized users with credentials
MCP Gateway
Requires API key (issued by IT)
How We Keep It Secure
No Password Login — Only SSH key authentication is allowed
Firewall — Only necessary ports are open
Regular Updates — Operating system kept up-to-date
Isolated Environments — AIC and Jetta data is kept separate
Logging — All access attempts are recorded
If You Lose Access
If your key stops working or you can't connect:
Don't panic — it's usually a simple fix
Contact IT for help
Never share your key with anyone else
If You Leave the Company
When employees leave, their access is immediately revoked by removing their SSH key from the server. There's no password to change — their key simply stops working.
Questions about access? Contact the IT administrator.
Server Setup Checklist
Track the progress of setting up this server for production use. Items are marked as complete when fully operational.