| Hey HN, I’ve built a database gateway to provide controlled access to production databases with fine-grained permissions and secure query execution. Key Features: - Role-Based ACLs: Define access rules at the instance, table, and column levels. - OIDC Authentication: Users log in through OpenID Connect. - Multi-Instance Support: Query multiple PostgreSQL instances from a single interface. - Web Interface: Execute approved queries and view results securely. - Query Storage: Save query results for later access or export. How It Works: - Users authenticate via OIDC. - ACLs enforce access to specific instances, tables, and columns. - Approved queries are executed, and results are stored securely. Built For: - Developers who debug production data. - Team Leads and Product Owners who access production data for reporting. - DevOps who run queries on behalf of other roles. - Security Engineers who ensure sensitive production data remains protected. Question: How do your developers access production databases, especially when the data is sensitive and critical to the company? |