Free access. Temporary service. Use with care.

By accessing the site, submitting a connection check, creating an instance, or using an instance, you agree to these terms and the Privacy Policy. If you do not agree, do not use the service.

mysql.odmin.biz is part of odmin.biz. Contact the operator through github.com/hitrov. Do not include passwords, private keys, bearer URLs, or other secrets in a public issue or message.

The service creates an isolated community-edition phpMyAdmin and Adminer pair, DbGate, CloudBeaver, or MySQL Shell GUI workload configured for one submitted MySQL connection, with optional SSH forwarding. The phpMyAdmin and Adminer URLs share one random instance ID and Pod. Each generated URL grants access to that connection while the workload exists.

The service is currently offered free of charge, without registration, a paid plan, a service-level agreement, guaranteed support, or any entitlement to capacity. Free availability may be limited, changed, suspended, or discontinued. Any future charge would require separate clear terms before it applies.

An instance has no guaranteed creation time, availability, or performance. An ordinary public instance is initially scheduled for permanent deletion, including its credentials, between 60 and 75 minutes after creation. An administrator may replace that mandatory deadline with another bounded deletion time. Administrator-launched instances and their public demos have no automatic expiry. Public-created instances cannot be promoted to demos, and their deletion schedule cannot be canceled. An administrator may restart, reconfigure, disable, or permanently delete any instance earlier, with or without notice, including for capacity, maintenance, security, abuse prevention, or no stated reason.

Workspace storage is ephemeral, there is no backup or recovery service, and Pod replacement can erase workspace state even while an instance remains listed. Closing a browser tab does not delete an instance. Ask the administrator to delete it as soon as the work is finished.

Use the service only with databases, servers, accounts, and SSH hosts that you own or are explicitly authorized to access. You are responsible for applicable law, workplace policies, provider terms, data-protection duties, and the consequences of every operation performed with the credentials you submit.

Do not use the service for unlawful access, credential attacks, exploitation, scanning, enumeration, denial of service, malware, harassment, infringement, or an attempt to bypass Turnstile, capacity limits, connection binding, or other safeguards.

Public tool guides explain the service but do not create a database, reserve capacity, verify a connection, or guarantee that a launch type is currently enabled. Search snippets and third-party indexes may be stale. Only the live launcher and its server-side checks determine availability and acceptance.

Do not place credentials, private keys, passphrases, bearer URLs, or connection details into a search engine or public link. The only supported launcher preset is the documented non-sensitive URL fragment, which is removed after parsing and never starts a connection automatically.

Use a dedicated least-privilege database account, a restricted SSH account when tunnelling, and current backups. The client is bound to the submitted connection, but it can perform any read or write that the submitted database account permits. You are solely responsible for queries, changes, deletions, disclosures, and data loss caused through that account.

The random instance URL is a bearer secret. Anyone who obtains it may access the instance without a separate mysql.odmin.biz login. Keep it out of shared messages, screenshots, logs, bookmarks synchronized to untrusted devices, and public notes.

Every instance exposes a bearer management page where anyone with the same private instance ID can view sanitized health information, recreate its Pod, or delete the whole instance. Pod recreation terminates current sessions and permanently erases ephemeral Pod storage. If an administrator publishes an instance as a public demo, its management page is available only to an authenticated administrator, who can view its health, recreate it, or delete it from the admin inventory. An explicitly enabled administrator-created unrestricted instance may also store up to five SSH-forwarded routes. Each requires verified SSH and database credentials. Database credentials are used only for connection testing and are not retained; additional SSH credentials remain available only to the tunnel supervisor until the route or whole instance is deleted. Adding or deleting one of these unrestricted routes normally does not restart the Pod.

On an administrator-enabled private restricted phpMyAdmin/Adminer, DbGate, CloudBeaver, or MySQL Shell GUI instance, the immutable original connection and up to four added verified profiles form a five-profile allow-list. Added MySQL credentials are retained in a dedicated Kubernetes Secret so the tool can use those profiles; optional SSH credentials remain available only to the tunnel supervisor. Adding or deleting a permanent profile, or enabling or disabling the feature, restarts the Pod and ends sessions and ephemeral workspace state. Public demos and unrestricted instances do not support permanent profiles; public-created restricted instances retain their mandatory deletion schedule.

No system is completely secure. Kubernetes Secrets are not inherently encrypted, the URL is not user authentication, the SSH flow currently uses trust on first use, and selected destination systems or infrastructure may record connection activity. Use the service only when those limits are acceptable for the data involved.

You must promptly stop using an instance and request deletion if its URL or submitted credential may have been exposed. The operator does not monitor your database for unsafe queries or maintain your backups.

phpMyAdmin, Adminer, DbGate, CloudBeaver, MySQL Shell Community and its GUI plugins, Cloudflare Turnstile, hosting and Kubernetes infrastructure, certificate authorities, registries, and the systems you select are provided or operated by third parties under their own licenses, terms, and privacy practices. Their names do not imply endorsement, partnership, or a guarantee from mysql.odmin.biz.

This is an independent community service and is not affiliated with, sponsored by, or endorsed by Oracle Corporation or its affiliates. Oracle and MySQL are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

To the maximum extent permitted by law, the service and every instance are provided “as is” and “as available,” without warranties of any kind, whether express, implied, or statutory, including accuracy, availability, security, confidentiality, non-infringement, merchantability, fitness for a particular purpose, or uninterrupted operation. No result, connection test, TLS endpoint, or ready status is a guarantee.

To the maximum extent permitted by law, the operator is not liable for indirect, incidental, special, consequential, exemplary, or punitive damages, or for loss of data, credentials, access, profits, revenue, opportunity, goodwill, or reputation arising from use or inability to use the service, deletion or replacement of an instance, third-party systems, unauthorized access, or reliance on any result.

Nothing in these terms excludes liability or statutory consumer and privacy rights that applicable law does not allow to be excluded or limited.

Access may be refused or terminated to protect the service, its users, third parties, or infrastructure, or to enforce these terms. Features, limits, safeguards, free availability, and these terms may change or be discontinued. The effective date at the top identifies the current version; continued use after a change means the updated terms apply to later use.