Ctrlk
TrustAPI Docs
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Architecture

While the GRAX Application interface is the main interface to backing up, protecting, and retaining your data, it's all powered by a single-tenant backend service that depends on an array of infrastructure components to perform successfully.

For a recap of GRAX features, business cases, or deployment options, see our product documentation.

High-Level Components

The basic architecture of GRAX is:

  1. Compute

  2. Persistent Blob Storage

  3. Persistent Indexed Storage

  4. External Connectivity

  5. Network Security Management

GRAX Simplified Architecture

The specific implementations of these simplistic labels can vary in both substance and complexity depending on deployment path chosen, platform of choice, and restrictions/regulations in place on all involved parties.

The guides in this section help explain the options you have in deploying GRAX, as well as enable your team to design, implement, and support the infrastructure yourself if so required.

High-Level Constraints

Operating outside the scope of these limitations causes issues with data integrity, data loss, contractual agreements, and general service availability:

  • Only one GRAX Application may be running for a given license.

  • Only one GRAX Application may be talking to the storage bucket and the Database.

  • Storage bucket performance must be on par with documented S3 performance metrics.

  • Egress to hq.grax.com must be available at all times, and the GRAX Application must remain online to receive updates. See below.

Continuous Availability

The GRAX Application updates itself every weekday. An offline application does not receive updates and drifts from the current release as long as it stays down. Extended drift may leave the application unable to function upon its return, at which point it must be redeployed and reimplemented.

Instance replacements, reboots, and short outages are expected and handled normally. Prolonged downtime is the risk. If you need to shut down a GRAX Application for an extended maintenance window, migration, or an infrastructure freeze, contact GRAX Support before doing so.

Last updated

Was this helpful?