Citadel. Management beyond a single site.
Citadel is the subscription service for partners and customers managing Atlas and Argos instances. Bring together your own installations or those of your customers, organize access and track system status from a central console.
Your instances, under control. At one site or across many.
Internal IT teams manage their own instances; MSPs and integrators manage customer installations. Citadel coordinates access, Atlas delivers services and Argos governs networking. Management connections remain separate from ordinary site traffic.
Service activation and use →Connect
Enter your organization’s or partner’s Citadel URL in the instance console.
Approve
Verify registration and confirm the code or authorized key.
Assign
Organize instances and assign groups and access rights.
Manage
Check status and open an authorized remote session.
Service access
Citadel is provided to partners and customers on a subscription basis. The central console is delivered as a service: it is not distributed for self-hosted installation and customers do not need to provision a Citadel server. The business or partner configures operators, connects authorized Atlas and Argos instances and manages their access. Contact EDON for activation and subscription terms.
A console for your business and your customers
Citadel serves both businesses administering their own infrastructure and MSPs or integrators managing systems for customers. An internal IT team can bring together its own Atlas and Argos instances, including installations across multiple sites, assign operator responsibilities and access consoles from a central point. Service providers can organize customers, groups and installations while retaining distinct access scopes.
Separate customers, explicit delegation
Group permissions determine allowed operations and partner scope. Customer users see instances shared with them and can receive a specific remote-access grant. Isolation is also enforced in database queries. Root and globally scoped groups of superadmin partners have broader privileges: this responsibility must be assigned deliberately.
From installation to managed instance
Linking starts in the Atlas or Argos console by entering the partner URL. Citadel verifies the instance registration and presents a request for approval by comparing a code. For planned installations, an enrollment key can authorize automatic approval. The system is then assigned to its customer and authorized operators. Registry verification is an operational requirement, not a certification of regulatory compliance.
Remote support through the product console
From an instance detail page, an authorized operator opens its Atlas or Argos console over a protected connection. The management tunnel has a TCP/443 fallback when UDP is unavailable. Remote access grants administrative privileges on the instance: Citadel controls who may start it, while work takes place in the product console. The link does not create a shared customer network or a site-to-site VPN.
Time-limited, checked and revocable access
Console access requires a second factor. Remote sessions last at most four hours and expire after thirty minutes of inactivity. Checks verify the session, operator permissions and instance state throughout use, with a short authorization cache. Revoking permissions, suspending an instance and disconnecting its link can terminate access through their respective control flows.
Installation status and operational priorities
The console collects instance-reported status and compares Atlas and Argos versions with those published in the repository. Notifications can flag instances going offline or returning, enrollment requests and operational deadlines. This helps prioritize checks and plan maintenance. An outdated version is information for the operator: it does not mean Citadel automatically performs coordinated updates across every appliance.
Traceability with attention to privacy
The activity log supports filtering and CSV export of recorded administrative changes and remote-access events. Partners, users, connection addresses and customer references are information that needs protection. Define who may access it and how it is retained. The log should not be confused with a session video recording or a complete inventory of every action inside the remote console.
Centralized management remains a choice
Atlas and Argos retain their own roles and local consoles. Citadel adds a coordination point for linked, authorized installations without becoming the path for ordinary business data. Losing the link prevents support through Citadel but does not move local service execution to Citadel. Version compatibility, revocation and recovery procedures must be tested in the chosen configuration; no SLA or HA capability is claimed.
These capabilities are documented in the source; they are not hardware certifications, benchmarks or availability guarantees. Verify configuration and workload during assessment.
Control starts with a conversation.
Tell us about your infrastructure. Let’s start with what you actually need.
Talk to an engineer