Use case · 100 icons
Icons for database content
Relational, document, key-value, graph, and vector database logos — for architecture diagrams, migration guides, and comparison posts.
Clickhouse
MongoDB
MySQL
PostgreSQL
Prisma
Redis
Snowflake
Sqlite
Supabase
AWS Aurora
Compose
Dgraph
Firebase
Forestadmin
Typeorm
Airtable
Aerospike
Algolia
Apache Impala
Appwrite
ArangoDB
AWS Athena
AWS CloudSearch
AWS DocumentDB
AWS DynamoDB
AWS ElastiCache
AWS Keyspaces
AWS Neptune
AWS OpenSearch
AWS RDS
AWS Redshift
AWS Timestream
Bing
Cassandra
Chroma
Couchbase
CouchDB
Database Labs
Datagrip
Datasette
DataSpell
DataStation
Dbt
DocSearch
Doctrine
Dolt
Drizzle
Edgedb
Elasticsearch
Etcd
Fauna
FoundationDB
Gun.js
Hadoop
Hasura
Hbase
Heroku Redis
Hibernate
Humongous
Influxdb
Kagi
Keydb
Knex
Lucene
Lucene.net
MariaDB
Meilisearch
Memcached
Metabase
Milvus
MindsDB
Neo4j
Neon
Nocodb
OpenSearch
Oracle
Osquery
Percona
Perplexity
Pinecone
Planetscale
PocketBase
PouchDB
Presto
Reindex
RethinkDB
Riak
Risingwave
RocksDB
RxDB
Sequelize
Singlestore
Solr
SurrealDB
Swiftype
Typesense
Upstash
Vitess
Xata
YugabyteDB
Every database post needs a logo. For an architecture diagram, place relational DBs (Postgres, MySQL, MariaDB) on one axis and NoSQL/document (MongoDB, DynamoDB) on another — readers scan the category split faster than they decode individual logos. If you're writing a "Postgres vs X" piece, use the compare pages instead, which already line up logos and metadata side-by-side.