MariaDB Business Source License 1 1 Text
You review the mariadb business source license 1 1 text to check usage rules. This license lets you run code with limits on production use. Engineering teams read these terms before they set up new database servers. Many teams then create broad admin accounts to set up the server fast. Broad accounts create big risks when engineers run live queries on production data. How the mariadb business source license 1 1 text works in practice The Business Source License is a middle ground between open
Your coding agents run with your access.
Claude Code reaches prod with a developer's credentials, and approval prompts get clicked through. hoop.dev checks every query, masks sensitive data, and holds risky changes for a human.
You review the mariadb business source license 1 1 text to check usage rules. This license lets you run code with limits on production use. Engineering teams read these terms before they set up new database servers. Many teams then create broad admin accounts to set up the server fast. Broad accounts create big risks when engineers run live queries on production data.
How the mariadb business source license 1 1 text works in practice
The Business Source License is a middle ground between open and closed code. You can read the source code and modify it for internal testing. The license text sets a change date for the software version. On that date, the code converts to an open source license. Before that date, the license limits how you use the software in production. Each vendor writes a specific grant that defines allowed production use. Teams must check the grant text inside the repo before deploying servers.
Once legal teams approve the license, admins set up database accounts and roles. Native MariaDB permissions work through user accounts tied to network hosts and roles. Admins grant read or write privileges at the database or table level. When a user logs in, the database checks their host and password. It loads the assigned role to decide which tables the user can read. Teams often group users into shared roles like developer, analyst, or admin. This setup controls who can log in and which schemas they can touch.
Why native roles leave a gap after license checks
Passing a license review and setting up roles only solves the first step. Native database grants decide who can log in and open a table. They do not inspect what individual queries do while a session is active. If a developer has read rights on a customer table, they read everything. Native permissions do not rewrite sensitive fields like emails or phone numbers. A single broad query can pull thousands of card numbers or national IDs.
Shared roles also make it hard to track who ran a bad command. When five engineers share one role, the database log shows one account name. You cannot tie a dropped table back to a specific person on your team. Static grants also stay active twenty-four hours a day. An account created for a quick fix keeps its write rights forever. Teams need a way to inspect queries in flight and mask sensitive results.
Snyk Open Source + Text-Based Session Recording: architecture patterns and best practices
Continue reading? Get the full guide.
Free. No spam. Unsubscribe anytime.
How to tighten database permissions during setup
Start by separating setup accounts from daily developer accounts on every server. Never let regular apps or users log in with the root account. Create small roles that only grant access to specific tables needed for work. Remove write rights from users who only need to check data for bugs. Review active database accounts every month and delete unused logins right away. Keep a clear log of every query that changes data or schema rules.
Check MySQL queries and results on the wire
MySQL grants control who logs in. They do not check single queries or mask sensitive columns once a session starts. With hoop.dev, you run an open-source proxy, a sidecar for your MySQL. It runs next to MySQL, RDS, or Aurora and reads the MySQL wire protocol.
Multi-statement batches and prepared queries are split and checked one by one by hoop.dev guardrails. When a rule refuses a query, MySQL returns a native error packet with your message. On the response path, hoop.dev data masking rewrites string values in returned rows that match your rules. Every query and decision is logged per resource. See the MIT-licensed project on GitHub.
Frequently asked questions
Is the Business Source License an open source license?
No, it is a source-available license with specific limits on production use. The code becomes open source only when it reaches the listed change date.
Where do I find the exact production rules in the license text?
Look for the additional use grant section near the top of the file. That section explains the exact production limits set by the software vendor.
Do license terms affect how MariaDB handles user permissions?
No, the license only covers legal rights to run or share the software. You still must set up database roles and query rules to protect data.
Related guides
In this post