Deployment & Requirements

This section explains how Lyntaris is deployed to customers and the specific hardware and network requirements depending on your chosen package and channel.

Deployment Architecture

Unlike traditional cloud-hosted SaaS platforms, Lyntaris is designed for maximum privacy and performance. The system is deployed locally on a dedicated Windows device at the client's location.

  • Zero Incoming Connections & High Security: We do not connect into your internal company network. All connectivity is outbound from the dedicated machine (to our relay for updates and to external LLM APIs via HTTPS).
  • Automated lifecycle: A small local agent on the machine polls your secure update relay, downloads platform packages, and applies them—including orchestrating the required containers—without manual steps. Component names and scripts are documented for integration engineers in the internal deployment guide.

Hardware Requirements

The hardware you need depends entirely on the Channels you intend to run. We separate deployments into two categories:

1. Lyntaris Platform (Text & Logic Only)

If you are deploying channels like Web Text chat, WhatsApp, or direct API integrations, you are only running the core HoloBrain orchestrator (Flowise and FastAPI backend).

  • Requirement: Standard modern Windows PC or light server. The core text and logic architecture is extremely lightweight and heavily optimized.

2. Unity Deployments (Avatars & Physical Kiosks)

If you are deploying channels that utilize the Unity 3D rendering engine—such as Physical Kiosks with Femto depth cameras, Desktop Apps with 3D avatars, or Call Centers running dozens of concurrent headless SIP agents—the system requires significantly more resources to maintain a zero-latency real-time conversational and visual loop.

  • Requirement: A powerful machine with at least 16 GB RAM, a strong multi-core CPU, and (for kiosks/avatars) a dedicated GPU capable of smooth 3D rendering.

Note: All deployments require sufficient SSD storage space for the platform files and local Vector Databases (document stores).

Network & Remote Access

  1. Outbound Internet: The dedicated device must have outbound access on port 443 (HTTPS).
  2. Remote Access: We require remote access software (e.g., RustDesk) installed on the dedicated machine. This is used by the Lyntaris team strictly for the initial setup, configuration, and occasional troubleshooting of the automated updater.
  3. Local Access: For basic local use, no firewall changes are required. The chat and platform UI are accessed via a browser on the same machine (e.g., http://localhost:8292).

Next Steps or Pilot Access

If you are running a PoC (Proof of Concept) on your own hardware, or your dedicated environment has just been provisioned, your Lyntaris administrator will provide:

  1. The local port (e.g., 8292) to access the builder UI.
  2. The initial authentication credentials to securely log in.

results matching ""

    No results matching ""