[rfc]: End-to-end Encryption#49
Merged
Merged
Conversation
robzienert
approved these changes
Jun 29, 2026
pseudomuto
added a commit
that referenced
this pull request
Jul 22, 2026
Add an RFC proposing how the Temporal Proxy will optionally compress workflow payloads before forwarding them upstream. Centralizing compression at the proxy lets operators enable it in one place, transparently to workflow developers, instead of building it into every Worker's Data Converter or a separate codec server. It composes with the proxy's encryption (always compressing before encrypting) and can help payloads stay under Temporal's per-payload and gRPC request size limits. The proposal covers the three supported algorithms (LZ4, ZSTD, Snappy) and why others are excluded, the per-payload metadata scheme that drives decompression, global and per-namespace configuration including per-namespace opt-out, and the observability metrics. Structure mirrors the encryption RFC (#49), with a reference to the overview RFC up top.
Add an RFC proposing how the Temporal Proxy will handle end-to-end encryption of workflow data (payloads, memo, and header fields). The proposal centralizes encryption at the proxy so operators manage and rotate keys in one place, transparently to workflow developers, rather than every team standing up its own codec server or building encryption into each Worker. <https://github.com/temporalio/temporal-proxy/blob/rfc-encryption/rfc/encryption.md>
pseudomuto
force-pushed
the
rfc-encryption
branch
from
July 22, 2026 16:06
7b0db8b to
11fc6e4
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add an RFC proposing how the Temporal Proxy will handle end-to-end encryption of workflow data (payloads, memo, and header fields).
The proposal centralizes encryption at the proxy so operators manage and rotate keys in one place, transparently to workflow developers, rather than every team standing up its own codec server or building encryption into each Worker.
https://github.com/temporalio/temporal-proxy/blob/rfc-encryption/rfc/encryption.md