Skip to main content
Goava
ع
Security & Deployment

Your data perimeter. Your rules.

For government and regulated organisations, the first question in any data governance project is where the metadata lives. Goava gives you a clear answer: fully inside your own data centre, or in cloud hosted within Saudi Arabia — with enterprise authentication and an audit-friendly activity history.

Request a demoSee NDMO alignment

Enterprise security, ready for procurement review

The controls your security and compliance teams will ask about — answered before they ask.

  • Role-based access control

    Fine-grained roles and policies define who can view, edit, and own every metadata asset — from a single table to an entire domain.

  • Single sign-on

    Connect your existing identity provider through OIDC, SAML 2.0, or LDAP. Access follows the identities and groups you already manage.

  • JWT API authentication

    Service-to-service and automation access is secured with JWT tokens, so pipelines and integrations authenticate as strictly as people do.

  • Audit-friendly activity history

    Every change to classifications, ownership, glossary terms, and descriptions is recorded in activity feeds — who changed what, and when.

  • Self-hosted on-premises

    Run the full platform inside your own data centre, within your network perimeter and under your operational control.

  • Cloud inside the Kingdom

    Prefer managed hosting? Deploy in a Saudi cloud region; no catalog data leaves your environment by default.

Deployment options

Metadata residency by design

For government entities, where metadata lives is the first procurement question — and it deserves a plain answer. Goava deploys fully on-premises inside your perimeter, or in cloud hosted inside Saudi Arabia. In both models, the platform catalogs metadata about your systems; your underlying data stays in the source systems where it already lives.

  • Fully on-premises: the entire platform runs inside your own data centre
  • In-Kingdom cloud: managed hosting on infrastructure located in Saudi Arabia
  • Metadata-only by design: source data is never moved into the catalog
  • Same platform, same features, in both deployment models
Discuss your deployment

Arabic-native operations

Your stewards work in Arabic

Goava ships with a native bilingual interface — Arabic with the ar-SA locale, and English — so your Data Management Office never has to choose between usability and adoption. Stewards can document, classify, and review in formal Arabic while technical teams work in English, on the same catalog.

  • Arabic interface with right-to-left layout, built on the ar-SA locale
  • Record each glossary term's Arabic and English names
  • Stewards classify, describe, and approve in the language they work in
  • Each user chooses their own language — one catalog, two languages
Explore governance features

Security and deployment questions

Bring governance inside your perimeter

Talk to our team about on-premises and in-Kingdom cloud deployment, and what a rollout would look like in your environment.

Request a demo