Skip to the content
Know your tech before you buy it. Makers: get listed from $49/mo

TIBCO Messaging Schema Repository for Apache Kafka

docs.tibco.com

  • Free plan
  • macOS
  • Linux
  • API
  • Self-hosted
7.3 Club score Visit docs.tibco.com

What TIBCO Messaging Schema Repository for Apache Kafka is

TIBCO Messaging Schema Repository for Apache Kafka is a self-hosted REST service for registering and managing schemas shared by producer and consumer applications. It uses Apache Avro JSON schema representation with Apache Kafka, checks compatibility as schemas evolve, and keeps schema versions so applications can use the appropriate message format. Compatibility policies include BACKWARD, BACKWARD_TRANSITIVE, FORWARD, FORWARD_TRANSITIVE, FULL, FULL_TRANSITIVE, and NONE, with BACKWARD as the default. OAuth2 roles control REST operations by default, and administrators can restrict access down to the subject level. The repository publishes REST documentation through OpenAPI and supports interactive requests with Swagger UI. TIBCO FTL supplies the required storage layer. Apache Kafka clients and brokers can use the repository for Avro schema management, while TIBCO Enterprise Message Service Kafka transports can retrieve schemas for deserializing imported Kafka payloads. Version 2.0.0 includes RPM, DEB, and tar packages for 64-bit Intel Linux and an installer for 64-bit Intel macOS; macOS x86-64 support is marked deprecated. TIBCO states support for version 2.0.0 ends April 30, 2027.

Who it suits

This repository suits teams running Apache Kafka applications that need centralized Avro schema registration, versioning, and compatibility checks. It is aimed at self-hosted Linux or Intel macOS deployments and organizations that can provide TIBCO FTL storage.

Good to know, and what to watch

  • Manages Apache Avro JSON schemas for Kafka
  • Retains versions as schemas evolve
  • Offers seven compatibility policy choices
  • Provides OAuth2 role-based REST access
  • Includes OpenAPI documentation and Swagger UI
  • TIBCO FTL is required for storage
  • macOS x86-64 support is marked deprecated
  • Community Edition excludes TIBCO Support
  • Version 2.0.0 support ends April 30, 2027

Enterprise Edition

—

Community Edition

Free

Free plan

Getting started

  1. Open the TIBCO user guide
  2. Install the Linux RPM, DEB, or tar package, or the Intel macOS installer
  3. Provide TIBCO FTL for repository storage
  4. Configure OAuth2 roles for REST operations
  5. Register and manage Avro JSON schemas through the REST API

Limits to check

The free Community Edition covers up to 100 application instances or 1,000 web/mobile instances in production and does not include TIBCO Support.

The Club's review

Overview

TIBCO Messaging Schema Repository for Apache Kafka is a self-hosted REST service for registering and governing Apache Avro schemas used by Kafka producers and consumers. It is most suitable for teams that need controlled schema evolution and already operate TIBCO infrastructure. The central qualification is that TIBCO FTL is required for storage, so this is not an independent registry you can drop into an otherwise unrelated stack.

Kafka clients and brokers can use it to manage Avro formats, while TIBCO Enterprise Message Service Kafka transports can retrieve schemas when deserializing imported Kafka payloads. That makes it particularly relevant to mixed Kafka-and-EMS estates. The documented validation scope is event, and deployment is self-hosted.

Key features

  • Avro-focused registry: Schemas use Apache Avro JSON representation, keeping the service aligned with Kafka message serialization rather than presenting a general multi-format catalog.
  • Evolution checks and version history: The repository validates changes for compatibility and retains schema versions. Producers and consumers can therefore select the format appropriate to a message instead of relying on an undocumented contract.
  • Seven compatibility modes: Administrators can use BACKWARD, BACKWARD_TRANSITIVE, FORWARD, FORWARD_TRANSITIVE, FULL, FULL_TRANSITIVE, or NONE. BACKWARD is the default. The transitive variants apply rules across the version history, while NONE removes compatibility enforcement when that is an intentional choice.
  • Role-based authorization: OAuth2 roles govern REST operations by default, with restrictions configurable down to the subject level. That is useful when different applications should manage or read only particular schema subjects.
  • REST tooling: OpenAPI documentation and an interactive Swagger UI make the API easier to inspect and exercise, which helps teams integrating the repository into deployment or application workflows.
  • Kafka and EMS connectivity: Kafka applications and brokers can manage schemas directly, and EMS Kafka transports can obtain them for imported payload deserialization. This is a practical advantage for organizations bridging those systems.

Pricing

The Community Edition is free at no cost. It supports up to 100 application instances, or up to 1,000 web/mobile instances, in production. The trade-off is explicit: TIBCO Support is not included, so it suits smaller deployments that can operate the service themselves.

The Enterprise Edition uses custom pricing. It includes all documented features, TIBCO Support, and enterprise production deployment. It is the appropriate tier when a production rollout needs vendor assistance or exceeds the Community Edition instance limits. No paid-plan price or trial term is stated.

Platforms

The service is offered as an API and is self-hosted on Linux or macOS. Version 2.0.0 provides 64-bit Intel x86_64 Linux packages in RPM, DEB, and tar formats, plus a 64-bit Intel macOS installer. macOS x86-64 support is marked deprecated, so new macOS deployments should account for that status.

TIBCO states that support for version 2.0.0 ends on April 30, 2027, with no product or security updates before that date. Customers can log support cases online, and live chat is available 24 hours a day, seven days a week, but Community Edition users do not receive TIBCO Support.

Who it's for

Choose it for Kafka teams that need governed Avro contracts, explicit compatibility policy, version retention, and subject-level access control in a service they run themselves. It is especially well matched to organizations already using TIBCO FTL or connecting Kafka with TIBCO EMS.

Look elsewhere if you cannot operate TIBCO FTL, want a managed registry, need a non-Avro schema focus, or are planning around a platform with a longer current support runway. The deprecated Intel macOS path is another concern for teams standardizing on newer Mac hardware.

Pros and cons

Pros

  • Strong evolution controls: Seven compatibility modes, including transitive options, let teams match enforcement to their release process.
  • Useful version retention: Consumers can obtain the schema version appropriate to the message they are reading.
  • Fine-grained access: OAuth2 roles and subject-level restrictions provide a clearer security boundary than a registry with only broad administrative permissions.
  • Free production entry point: Community Edition covers up to 100 application or 1,000 web/mobile instances without a license charge.

Cons

  • Mandatory TIBCO FTL dependency: The required storage layer prevents a lightweight standalone deployment.
  • Community support gap: The free edition excludes TIBCO Support.
  • Limited platform outlook: macOS x86-64 is deprecated, and version 2.0.0 support ends April 30, 2027.
  • Self-hosting responsibility: Teams must run and maintain the service rather than handing operations to a managed provider.

Alternatives

Browse Schema Registry Software when you want a wider comparison before committing to a deployment model.

  • Lenses is a better fit when you need a broader platform footprint, including web and Windows, plus a free trial; its K2K Community plan limits replication to five topic partitions and provides at-least-once delivery.
  • Buf Schema Registry suits teams wanting a web-accessible, API-first service with one private repository and unlimited public repositories on its free Community plan.
  • Confluent Cloud is preferable when managed Kafka clusters, autoscaling resources, and managed connectors matter more than running a registry yourself.
  • Google Cloud Pub/Sub is an alternative for teams choosing a managed messaging service with a 10 GiB free-usage allowance.
  • Sourcemeta One offers a free self-hosted Community edition on Linux and web, with a subset of functionality.
  • Apache Pulsar is a free, open-source messaging platform when you are evaluating a broader alternative to Kafka-centric infrastructure.
  • AxonOps Schema Registry is a free, Apache 2.0-licensed self-hosted registry for teams seeking that licensing model.
  • Karapace is a free self-hosted option with a 250 KiB/s throughput cap, three-day retention, and limits of five topics with two partitions each.

Verdict

TIBCO Messaging Schema Repository for Apache Kafka is a sensible choice for TIBCO-centered Kafka environments that need disciplined Avro compatibility management, retained versions, and subject-level authorization. Its free Community Edition lowers the entry cost, but the required TIBCO FTL storage, self-hosted operations, deprecated Intel macOS support, and April 2027 support end date are substantial reasons to choose another registry when those constraints do not fit.

The verdict

Choose the Schema Repository when Kafka producers and consumers need governed Avro formats, compatibility validation, and version history in a self-hosted service. Consider another deployment if you cannot run TIBCO FTL or require a currently supported macOS x86-64 release.

Questions people ask

Is TIBCO Messaging Schema Repository free?

The Community Edition is free and has production limits of 100 application instances or 1,000 web/mobile instances.

Which schema format does it use?

It uses the Apache Avro JSON schema representation used with Apache Kafka.

What compatibility modes are available?

Available policies are BACKWARD, BACKWARD_TRANSITIVE, FORWARD, FORWARD_TRANSITIVE, FULL, FULL_TRANSITIVE, and NONE. BACKWARD is the default.

Which operating systems can run version 2.0.0?

Packages are provided for 64-bit Intel Linux, and an installer is provided for 64-bit Intel macOS. macOS x86-64 support is marked deprecated.

Does it integrate with Kafka?

Apache Kafka clients and brokers can use it for Avro schemas. TIBCO Enterprise Message Service Kafka transports can also retrieve schemas for deserialization.

What the maker publishes

Access control
By default, OAuth2-based roles control access to REST operations, including restrictions down to the subject level. source
Authorization
By default, access is controlled through OAuth 2 roles for REST operations, with restrictions configurable down to the subject level. source
Authorization
OAuth2 authorization uses signed JWT access tokens with asymmetric validation keys and can return 401 or 403 responses for unauthorized requests. source
Company founding
TIBCO’s site states that Vivek Ranadivé founded TIBCO in 1997. source
Company headquarters
TIBCO lists its headquarters at 2623 Camino Ramon, Suite 200, San Ramon, California 94583, United States. source
Compatibility policies
The documented compatibility policies include backward, forward, full, transitive variants, and none; the default is BACKWARD. source
EMS integration
TIBCO Enterprise Message Service Kafka transports can connect to the Schema Repository to obtain Avro schemas for deserializing imported Kafka payloads. source
Kafka integration
Apache Kafka client applications and Kafka brokers can use the repository to manage Avro schemas. source
Linux platform
Version 2.0.0 is available for 64-bit Linux on Intel x86_64 and includes RPM, DEB, and tar packages. source
macOS platform
Version 2.0.0 is available for 64-bit macOS on Intel x86_64. source
Purpose
The Schema Repository is a RESTful service for registering and managing schemas used for compatible message formatting between producer and consumer applications. source
REST API
The repository exposes REST API documentation through OpenAPI and supports interactive queries using Swagger UI. source
Schema evolution
The repository checks schema compatibility as schemas evolve and retains versions so applications can use the correct message format. source
Schema format
Schemas use the Apache Avro JSON schema representation used with Apache Kafka. source
Storage dependency
TIBCO FTL provides storage and is required to run the Schema Repository. source
Support access
TIBCO says customers can log support cases online, and live chat is available 24 hours a day, 7 days a week for other assistance. source
Support channels
TIBCO says customers can log support cases online and use live chat 24x7. source
Supported installation platforms
Installation documentation describes Linux package or TAR installation and a 64-bit Intel macOS installer; macOS x86-64 support is marked deprecated in release 2.0.0. source
Support status
TIBCO states support for version 2.0.0 ends April 30, 2027, and that product updates including security updates will not be provided before then. source

Checked against the maker's pages on 30 Sept 2026.