Listing Thumbnail

    LibreDB Studio

     Info
    Sold by: LibreDB 
    Deployed on AWS
    AWS Free Tier
    Open-source SQL IDE for cloud-native teams. One interface for 16 engines, among them PostgreSQL, MySQL, Oracle, SQL Server, MongoDB, Redis, ClickHouse and Trino. Browse schemas, run queries with schema-aware autocomplete, compare schemas, and generate SQL with AI assistance. Runs on your own instance; no data leaves your account.

    Overview

    LibreDB Studio is an open-source SQL IDE that your team runs on its own instance. One interface connects 16 database engines, so nobody needs a different tool for each of them.

    Engines: PostgreSQL, MySQL, Oracle, SQL Server, SQLite, MongoDB, Redis, Couchbase, ClickHouse, Apache Druid, Elasticsearch, OpenSearch, Apache Cassandra, Trino, libSQL and DuckDB.

    What you get:

    • Schema browsing, a query editor with schema-aware autocomplete, query history and result grids
    • Schema comparison between two connections
    • ER diagrams and data profiling
    • Optional AI assistance for writing SQL. It calls whatever model endpoint you configure with your own key; the product ships with none configured and is fully functional with AI switched off.
    • Optional OIDC single sign-on

    Where your data goes: nowhere. The instance is yours. Connections, query history and results stay on it, the software sends no telemetry, and the seller has no access to your instance - no keys, no agent, no callback. The credential fields in the local store are sealed with AES-256-GCM under a key that lives outside the store file.

    Deployment: launch the AMI, open port 3000 to your own network, and sign in with the administrator password generated on first boot for that instance alone. Change it immediately - the usage instructions say how, and where every sensitive file lives.

    MIT licensed. Source, documentation and issues: https://github.com/libredb/libredb-studio 

    Highlights

    • Sixteen engines behind one interface, among them PostgreSQL, MySQL, Oracle, SQL Server, MongoDB, Redis, ClickHouse and Trino.
    • AI query assistance using your own model key, or run it with no AI at all.
    • Self-hosted on a single instance: connections, query history and results stay in your account.

    Details

    Sold by

    Delivery method

    Delivery option
    64-bit (x86) Amazon Machine Image (AMI)

    Latest version

    Operating system
    Ubuntu 24.04

    Deployed on AWS
    New

    Introducing multi-product solutions

    You can now purchase comprehensive solutions tailored to use cases and industries.

    Multi-product solutions

    Features and programs

    Financing for AWS Marketplace purchases

    AWS Marketplace now accepts line of credit payments through the PNC Vendor Finance program. This program is available to select AWS customers in the US, excluding NV, NC, ND, TN, & VT.
    Financing for AWS Marketplace purchases

    Pricing

    LibreDB Studio

     Info
    This product is available free of charge. Free subscriptions have no end date and may be canceled any time.
    Additional AWS infrastructure costs may apply. Use the AWS Pricing Calculator  to estimate your infrastructure costs.

    AI Insights

     Info

    Dimensions summary

    This listing bills through a single dimension tied to running the software on a t3.small instance, charged per hour. The software itself is free, so your cost comes from the compute hours you use, not from a license fee or feature tier. There are no separate plans, upgrades, or add-on charges here. Every capability ships in one build, and running it beside your database in a container is what generates the hourly usage. Pricing scales only with how long you keep the instance running.

    Top-of-mind questions for buyers

    The rate covers running the software on one t3.small instance, billed per hour it runs. LibreDB Studio runs as a single container beside your database. Each hour the instance stays running counts toward your bill. The software itself is free, so charges track compute time only.
    Hourly software charges accrue only while the instance runs. A stopped or powered-off instance does not accrue running-time charges. Stopped instances may still incur underlying AWS storage fees for attached volumes, but the software metering follows running time only.
    No. Every capability ships in one build — single sign-on, role-based access, ER diagrams, the AI assistant, the database agent, and all supported database drivers. Nothing is held behind an upgrade. Your only cost is the hourly compute for the t3.small instance running the container.
    libredb.org+2
    Helpful?

    Vendor refund policy

    LibreDB Studio is offered at no charge on AWS Marketplace. No software fees are collected, so no refunds apply. Buyers pay only the Amazon EC2 infrastructure costs of running the instance, which are billed by AWS. For questions about this policy, contact info@sekoya.tech .

    How can we make this page better?

    Tell us how we can improve this page, or report an issue with this product.
    Tell us how we can improve this page, or report an issue with this product.

    Legal

    Vendor terms and conditions

    Upon subscribing to this product, you must acknowledge and agree to the terms and conditions outlined in the vendor's End User License Agreement (EULA) .

    Content disclaimer

    Vendors are responsible for their product descriptions and other product content. AWS does not warrant that vendors' product descriptions or other product content are accurate, complete, reliable, current, or error-free.

    Usage information

     Info

    Delivery details

    64-bit (x86) Amazon Machine Image (AMI)

    Amazon Machine Image (AMI)

    An AMI is a virtual image that provides the information required to launch an instance. Amazon EC2 (Elastic Compute Cloud) instances are virtual servers on which you can run your applications and workloads, offering varying combinations of CPU, memory, storage, and networking resources. You can launch as many instances from as many different AMIs as you need.

    Version release notes

    Initial listing of LibreDB Studio 0.14.1 on AWS Marketplace, so there is no upgrade path from an earlier version here. Ubuntu 24.04 LTS with the published container image pinned by digest. Application release notes: https://github.com/libredb/libredb-studio/releases/tag/0.14.1 

    Additional details

    Usage instructions

    1. LAUNCH Launch with the recommended security group: TCP 3000 and TCP 22, scoped to your own network. No user data is needed. First boot takes about a minute: it generates an administrator password unique to this instance, starts the app, then prints a banner.

    2. SIGN IN Open http://<instance-public-ip>:3000 and sign in as admin@libredb.org . Get the generated password either way:

    • No SSH key: EC2 console -> Actions -> Monitor and troubleshoot -> Get system log. The banner is printed there. This is the one place the password is published; anyone with ec2:GetConsoleOutput can read it.
    • SSH as ubuntu: sudo cat /etc/libredb-studio.info
    1. CHANGE THE PASSWORD NOW There is no in-app password change. Edit the file and restart: sudo nano /etc/libredb-studio.env sudo systemctl restart libredb-studio Change ADMIN_PASSWORD (and ADMIN_EMAIL if you want your own). Plain KEY=value lines, no quotes. Edit rather than sed: a password with / or & corrupts the line. Rotating JWT_SECRET is destructive: it invalidates sessions AND makes saved connection credentials unreadable, because the key that seals them derives from it.

    2. WHERE YOUR DATA LIVES

    • /opt/libredb/data/libredb-storage.db - saved connections. Secret fields (passwords, connection strings, TLS keys, SSH keys) are sealed with AES-256-GCM under a key derived from JWT_SECRET; host, port, database name and query history are stored as written.
    • /etc/libredb-studio.env (0600) - administrator password and JWT_SECRET.
    • /var/lib/docker/containers/<id>/config.v2.json - the runtime's copy of that file; redact before sharing docker inspect output. The key sits outside the store file, so the database file alone does not disclose credentials - but both are on the one root volume, so an EBS snapshot captures both. EBS encryption is available at launch. Backup: stop the service, archive the data directory AND the env file together, start it again. Restoring the data without the env file leaves the saved credentials unreadable.
    1. HEALTH sudo docker inspect -f '{{.State.Running}}' libredb-studio curl -fsS http://127.0.0.1:3000/api/db/health  curl -fsS http://127.0.0.1:3000/login  systemctl status libredb-studio ; sudo docker logs libredb-studio The health route answers without touching the database, so all three together are what tells you the instance is healthy. docker needs sudo: the ubuntu user is deliberately not in the docker group.

    2. ADDRESS, TLS, SSH Stopping and starting the instance assigns a new public IP; credentials are unaffected and the login greeting shows the current one. Use an Elastic IP or a load balancer for a stable address. The AMI serves plain HTTP on 3000 and sets AUTH_COOKIE_SECURE=false, because an instance with no DNS name cannot get a certificate at first boot. The session cookie travels in cleartext: keep the security group scoped to your own network, and put an ALB or CloudFront with an ACM certificate in front for TLS. SSH password authentication and root password login are disabled in the image. The seller has no access to your instance: no key, no agent, no callback.

    3. DEPENDENCIES, COST, QUOTAS, UPGRADES A normal launch reaches no registry; the application image is baked in and pinned by digest. The only outbound connections are the ones you configure: your databases, and an LLM endpoint if you set LLM_API_URL. The product ships with no model configured and works fully with AI off. The software is free; you pay AWS for instance hours, the 20 GiB gp3 volume and data transfer. One instance, one volume, one security group - check your EC2 and EBS quotas before launching. New versions ship as new AMI versions. To move: launch from the new version, copy /opt/libredb/data and /etc/libredb-studio.env across, start the service. There is no in-place upgrade.

    Support

    Vendor support

    Support is provided by LibreDB. Email info@sekoya.tech  for account and listing questions. Report bugs and feature requests at https://github.com/libredb/libredb-studio/issues , where maintainers respond publicly. Documentation:

    AWS infrastructure support

    AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.

    Similar products

    Customer reviews

    Ratings and reviews

     Info
    0 ratings
    5 star
    4 star
    3 star
    2 star
    1 star
    0%
    0%
    0%
    0%
    0%
    0 reviews
    No customer reviews yet
    Be the first to review this product . We've partnered with PeerSpot to gather customer feedback. You can share your experience by writing or recording a review, or scheduling a call with a PeerSpot analyst.