Guidewire Cloud terminology

Guidewire Cloud uses an astronomy metaphor for classifying Cloud Platform resources.

The following example shows how resources are named and organized within Guidewire Cloud:

• Insurance Company has a tenant located in a galaxy that operates within an isolation zone.
• The tenant has two stars, each representing a different business unit.
• Stars have planets on DEV, UAT, QA, PREPROD, and PROD orbits.

Isolation zone

An isolation zone is a group of galaxies designed to deliver a full set of Cloud Platform features within a specific geographic and regulatory boundary. Isolation zones are created mainly to support data sovereignty and meet regional compliance requirements, ensuring that data doesn't cross boundaries between regions.

Tenant

A tenant represents your company’s presence in a specific isolation zone in Cloud Platform. Due to regulations around data residency and security, each tenant is limited to a single isolation zone. Tenants are completely isolated from each other, so there is no sharing of data, configuration, or workloads between them. If your company needs to operate in different isolation zones, Guidewire creates a separate tenant for each isolation zone.

Examples: acme, claimwise.

Galaxy

The geographical region of the Guidewire Cloud infrastructure. Each galaxy represents a region with its own dedicated data centers.

Examples: Cartwheel (Paris, FR) , Fireworks (London, GB), Milky Way (Tokyo, JP).

Star

A star represents a business unit or shared service within your company that you want to manage independently on Cloud Platform. Each star is kept completely separate from the other stars, allowing you to keep different parts of your business operations independent while still operating under the same tenant.

Star system

A star system is a group of planets that share Cloud Platform services. You can have multiple star systems, and each star system keeps its data separate from the other star systems. Each star system has its own dedicated database. For details, see Stars and star systems.

Orbit

An orbit of a planet or asteroid represents code promotion paths or stages within the software development lifecycle (SDLC). Orbits can also specify attributes such as the number of CDA connectors. Cloud Platform supports the following orbits:

• Prod
• PreProd
• Dev
• UAT
• QA

For details, see View all planets.

Planet

A planet is an environment where you deploy and run code, such as InsuranceSuite, EnterpriseEngage, or InsuranceNow applications. All of your work is done on a planet. A star system can contain multiple planets, each for a different purpose or application. For example, you might have one planet for development and another for testing. Only one planet can operate on a production orbit. For details, see View all planets.

Planet names can be up to 10 characters long. Examples: dev, qa, test, claimsint.

Asteroid

Asteroid is a special type of planet that is designed to support workloads other than InsuranceSuite, EnterpriseEngage, or InsuranceNow applications. Asteroids support workloads:

• Containerized for operation on Cloud Platform.

• Created by Guidewire, your company, or third-party software providers.

Planets and asteroids can share orbits.

Additional terms

Guidewire Cloud uses the following additional terms:

• Tool

  The tool or service name. For example, pc, scm.

• Role

  The application permissions for users. For example, user, admin.