One API Key, Many Tenants: How We Isolate DeepL Translations Across Customers
Blog post from Rasepi
Rasepi addresses the challenge of tenant isolation in a multi-tenant SaaS environment by managing a single DeepL API key for all tenants, while ensuring that tenant-specific glossaries and style rules do not mix. This is achieved by storing all configuration data in a tenant-scoped database, where the database acts as the source of truth, and the DeepL API serves merely as a runtime execution target. This design employs EF Core global query filters to scope reads to the current tenant, preventing data from different tenants from leaking into each other. The system uses an "IsDirty" flag to mark entries that require synchronization with DeepL, executing updates only when necessary to avoid unnecessary deletions and recreations due to DeepL's immutable glossary constraints. Style rules and glossaries are isolated per tenant through tenant-specific IDs, and translation processes incorporate block-level caching to minimize redundant API calls. Despite the possibility of using separate API keys for each tenant, Rasepi opts for a shared infrastructure to leverage cost efficiencies and operational simplicity, relying on its internal mechanisms to maintain strict isolation between tenant data.
No tracked trend matches for this post yet.
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.