• Docs
  • Changelog
Sign in
Get started
    • Home
    • Your first deploy
    • Free instances
    • Platform features by plan
    • Use with coding agents
    • FAQ
    • Templates
      • Migrate from…
        • Heroku
        • Railway
    • Compute plans
    • SandboxesBeta
      • Service types
        • Which to use?
        • Static sites
        • Web services
        • Private services
        • Background workers
        • Cron jobs
        • Workflows
        • Multi-service architectures
      • Data storage
        • Render Postgres
        • Render Key Value (Redis®-compatible)
        • Persistent disks
    • How deploys work
    • Supported languages
    • Git providers (GitHub, etc.)
    • Build pipeline
    • Deploy hooks
    • Monorepo support
    • Troubleshooting deploys
      • Previewing changes
        • Single-service previews
        • Preview environments (multi-service)
      • Docker deploys
        • Overview
        • Deploy a registered image
        • Using secrets
      • Runtime
        • Native runtimes
        • Environment variables & secrets
        • Default environment variables
    • Intro to sandboxes
    • Limits
      • How to…
        • Create & configure sandboxes
        • Execute commands
        • Manage files
        • Manage snapshots
      • Use with…
        • Claude Managed Agents
        • Cursor Cloud Agents
        • OpenAI Agents API
      • SDK/CLI reference
        • TypeScript SDK
        • Python SDK
        • CLI commands
    • Intro to workflows
    • Tutorial
    • Limits & pricing
      • How to…
        • Define tasks
        • Define flowsNew
        • Trigger runs
        • Develop locally
      • SDK reference
        • TypeScript SDK
        • Python SDK
      • Example workflows
        • TypeScript examples
        • Python examples
    • Overview
    • Create & connect
    • Database credentials
    • Extensions
    • Version upgrades
    • Logical replication
    • Legacy instance types
      • Database recovery
        • Recovery & backups
        • High availability
      • Database performance
        • Read replicas
        • Connection pooling
        • Admin apps
        • Repacking tables
        • Troubleshooting performance
    • Regions
    • Inbound IP rules
    • Edge caching
    • WebSockets
    • TLS certificates
      • Custom domains
        • Overview
        • Cloudflare
        • Namecheap
        • Other DNS providers
      • Internal traffic
        • Private network
        • Private links
      • Outbound traffic
        • Default IP ranges
        • Dedicated IP addresses
        • Outbound bandwidth
        • Handling network changes
      • Static site config
        • Custom response headers
        • Redirects & rewrites
    • The Render Dashboard
    • SSH / Shell access
    • Projects & environments
      • Service actions
        • Scaling
        • Rollbacks
        • Maintenance mode
        • One-off jobs
      • Infrastructure as code
        • Blueprints overview
        • render.yaml reference
        • Terraform provider
    • In-dashboard metrics
    • Health checks
    • Uptime best practices
      • Logging
        • In-dashboard logs
        • Log streams (syslog/HTTPS)
      • OpenTelemetry (OTel) metrics
        • Provider setup
        • Metrics reference
      • Notifications
        • Webhooks
        • Email / Slack
    • MCP Server
      • Render CLI
        • Overview
        • Command reference
      • REST API
        • Overview
        • API reference
      • Third-party connections
        • OIDC support
        • Datadog
    • Workspaces, members, & roles
    • Login settings
    • Audit logs
      • Organizations
        • Overview
        • SAML SSO
    • DDoS protection
    • Platform maintenance
      • Compliance
        • Overview
        • HIPAA (US health data)
        • HIPAA best practices
        • Shared responsibility model
        • Pentest policy
    • Heroku vs Render
    • Vercel vs Render

Deploy Adminer on Render

Adminer is a lightweight database management tool for MySQL, MariaDB, PostgreSQL, SQLite, Elasticsearch, and more.

You can deploy Adminer on Render to easily manage your PostgreSQL, MySQL, and Elasticsearch instances.

Deployment

  1. Fork render-examples/adminer on GitHub (or click the green 'Use this template' button).

  2. Create a new Web Service on Render, and give Render permission to access your new repo.

  3. Make sure the Language field is set to Docker, and enter a name for the service.

Click Save and you're good to go! When it's ready, your Adminer instance will be available at its unique onrender.com URL, and you can use it to connect to your private services on Render.

As an example, if your MySQL database is set up as a private service with url mysql-demo:3306 and username and database mysql, you can log in to it using the values below:

Adminer Login Screen

You will see your database in Adminer once you're logged in:

Adminer UI

You can also use Adminer to connect to other databases in your Render account. See Adminer docs for details.

Plugins

Adminer has a robust plugin ecosystem. Render's Dockerfile includes the following plugins by default:

  • dump-alter
  • dump-json
  • dump-zip
  • dump-bz2
  • tables-filter

Add more plugins by changing the value of ADMINER_PLUGINS in your version of the Dockerfile. You can also override the default set of plugins by setting the ADMINER_PLUGINS environment variable for your Render service.

Security

Because your Adminer URL is accessible over the internet, make sure to secure it with one of the following plugins:

  • Login IP
  • Login OTP
  • Login Table

These plugins need additional configuration described in loading plugins in the official Adminer Docker guide.

Deploy Adminer on Render
  • Deployment
  • Plugins
  • Security
All Systems Operational
© Render Inc. All rights reserved.