Service, support, and compatibility

On this page

Service responsibilities

Golden is a SaaS product operated by Trazadera. Customers use and configure the product; they do not deploy, patch, monitor, back up, or recover the underlying platform.

Shared responsibility

Trazadera operates	Customers control
Golden application and service infrastructure	Users, roles, and access tokens
Platform deployment, maintenance, and patching	Entities, tables, resources, and schedules they configure
Internal availability monitoring and incident response	Source-system access and the quality of submitted data
Platform backup and service recovery	Integration code, client-side retries, and secret storage
Managed service releases	Validation of business outcomes and downstream use of mastered data

Trazadera’s operational responsibility does not remove the need for customers to protect credentials, assign least privilege, review destructive actions, and retain source or downstream data according to their own governance obligations.

Environments and service terms

Use only the Golden HTTPS URL and environments assigned to your organization. Do not infer region, isolation, capacity, retention, availability, recovery, or support commitments from product behavior or this technical guide.

The applicable service agreement and approved assurance material are authoritative for service levels, data location, recovery objectives, security assurance, and plan-specific limits. Obtain that material through the approved Trazadera customer channel.

Customer-visible operations

Customers can monitor Golden outcomes through entity state, tasks, schedules, product events, metrics, history, and audit information. These are product signals, not infrastructure health or Trazadera incident-management interfaces.

Use Monitor Golden operations to interpret those signals. Do not probe undocumented health paths or build an integration against internal monitoring behavior.

Request support

Use the support channel agreed for your organization. When email is the approved channel, contact support@trazadera.com and include only:

the Golden product version and affected environment name;
the time range and operation;
affected entity, table, resource, task, or event identifiers;
the HTTP status and X-Trace-Id; and
sanitized validation or error messages.

Never send passwords, bearer tokens, authorization headers, complete customer records, or unapproved internal diagnostics.

Supported integrations

The supported customer integration surface consists of the operations and behaviors described in this documentation for the managed Golden SaaS release.

Supported sources of contract

Use the authored documentation for supported workflows, roles, safety boundaries, and compatibility guidance.
Use the curated Golden API reference for public operation parameters and schemas, or download its OpenAPI JSON for tooling.
Where enabled, use the running interactive explorer to inspect or test the service you are calling.
Use GET /api/configuration/version to identify the target release.
Use GET /api/resources/describe/{type} for resource property names and defaults, and GET /api/resources/enums for roles and configured resource references.

GET /api/configuration/openapi returns the live OpenAPI definition from the running Golden service. It is the source-level contract and can contain framework operations that are not supported customer workflows. The contract published on this documentation site is the curated customer projection.

Compatibility expectations

Clients should tolerate additional response properties, avoid parsing localized message text, and handle documented status codes and asynchronous outcomes. Pin the contract used for generation and rerun integration tests when release communication identifies a relevant API change.

An operation visible only in the running explorer does not establish support for customer use. Use the published API reference to determine the supported operations and their authentication requirements.

No numeric deprecation period or service-level commitment is established by this technical guide. The applicable service agreement and an explicit Trazadera release notice are authoritative for those commitments.

Client libraries and command-line tools

Golden does not currently offer a standalone Java client or goldencli as part of this public support surface. Use the REST API, an approved HTTP client, or an artifact and compatibility statement supplied directly with your deployment. Do not infer coordinates, package names, or support from implementation artifacts.

Outside this policy

Private configuration, internal endpoints, source structure, algorithms, deployment topology, monitoring implementation, and incident procedures are not public interfaces. Golden also does not document a general SQL-like table query language or a generic change-feed endpoint. A capability absent from this documentation requires confirmation from Trazadera before customer use.

Release and compatibility guidance

Trazadera deploys and operates Golden SaaS releases. Customers do not install, patch, back up, or roll back the Golden platform.

This documentation and its public API contract are verified against the Golden version named in the footer of every page, alongside the date the documentation was last reviewed against it.

Compare the documented version with your environment before adopting a version-dependent operation or configuration.

curl --fail-with-body --silent --show-error \
  --header "Authorization: Bearer ${GOLDEN_TOKEN}" \
  "${GOLDEN_URL}/api/configuration/version"

Managed release model

Release scheduling, service-level commitments, and any guaranteed notice period are governed by the applicable service agreement and Trazadera release communication. This technical guide does not establish additional contractual timelines.

When a release requires a customer action, the release communication should identify the affected capability and the action. Customers remain responsible for updating their integrations and configured Golden resources.

API compatibility

The published OpenAPI contract is the curated customer surface for Golden 3.0.0. Clients should:

tolerate additional response properties;
avoid parsing localized message text;
use documented enum values and status codes;
follow asynchronous operations to a terminal state; and
pin the contract used to generate or test a client.

The running /api/configuration/openapi operation returns the live OpenAPI definition. Use the public contract from this documentation site when deciding which operations are supported customer integrations.

Customer release checklist

After receiving a release notice relevant to an integration:

Identify the affected operations, schemas, resources, or workflows.
Compare the newly published public contract with the version pinned by the integration.
Regenerate a client only when the contract used by that client changes.
Run representative read and write tests in an approved non-production environment when one is assigned.
Confirm task completion and downstream outcomes for asynchronous workflows.
Keep credentials for different environments separate while testing.

Customers do not perform a Golden platform rollback. If a managed release causes a service problem, preserve the X-Trace-Id and customer-safe evidence, then follow the Golden SaaS support path.