Skip to main content

Our Secure Foundation: The Cloud Architecture

This guide explains the "physical" structure of the Hestia cloud. Even though it's all digital, think of it like a secure office building with different rooms for different jobs.

1. The Building Blocks (Containers)​

We use Docker Containers to keep different parts of our system separated. This way, if one part needs an update, the rest of the building stays open.

  • The Lobby (Nginx): The front door that handles all incoming traffic and directs it to the right room.
  • The Main Office (API): Where the "logical" work happens—checking permissions and processing your requests.
  • The Post Office (Mosquitto): The hub that sends and receives messages from your smart devices.
  • The AI Studio (HX47 Sidecar): A special, isolated room where the AI Brain does its thinking.

2. The Records Department (Databases)​

We use two types of storage to keep things organized:

  • The Quick-Access Desk (Redis): Stores things we need right now, like your current online status. It's built for lightning speed.
  • The Secure Vault (Firestore): Stores the permanent records, like your account settings and device history. It's built for absolute reliability.

3. The Security Camera (Audit Trail)​

We maintain a Tamper-Proof Log of every important event.

  • Every entry in the log is linked to the one before it with a "digital chain."
  • If anyone tried to delete or change an old entry, the chain would break, and we would know immediately.

4. Measuring Health (Metrics)​

We have dozens of "health monitors" running 24/7. They track things like:

  • How many commands are being sent?
  • How many devices are online?
  • Is the system slowing down?
  • Are there any failed security checks? If any of these numbers look unusual, our engineering team is notified instantly.

5. Built for Growth​

Our foundation is built to be Scalable. This means if the number of users doubles overnight, we can simply "add more lanes" (more API instances) to handle the load without any downtime.