Services
33 services, on the cluster you already own.
Pick one from a project's catalog and Anyport provisions it in that project, generates its credentials into a secret there, and hands your apps the connection as environment variables. There is no per-service fee: on a cluster you attach it runs on your hardware, and on Anyport Cloud it is billed as the compute it uses.
Every entry below ships today. Each page lists the options the console offers, in the catalog's own numbers, and the variables a bound app receives.
01Databases
Databases
Relational, document, graph, time-series, analytical and vector stores, each provisioned with its own volume inside the project that uses it.
- PostgreSQLPostgreSQL managed by CloudNativePG, with failover, pgvector, PostGIS and extensions you switch on from the database's own settings.Read about PostgreSQL →
- MySQLMySQL managed by the Percona operator, fronted by a connection proxy and backed up to an object store you own.Read about MySQL →
- MariaDBMariaDB managed by the MariaDB operator, speaking the MySQL protocol so every MySQL driver connects unchanged.Read about MariaDB →
- MongoDBMongoDB managed by the Percona operator, run as a replica set with a volume per member.Read about MongoDB →
- ClickHouseClickHouse for analytics: aggregations over billions of rows, managed by the Altinity operator.Read about ClickHouse →
- QuestDBTime-series in SQL: sensor readings, market ticks and events by the billion, ingested over ILP and read through any Postgres client.Read about QuestDB →
- InfluxDBTime-series for metrics, sensor readings and events, queried with Flux or InfluxQL and expired by bucket retention.Read about InfluxDB →
- Neo4jGraph database for connected data: relationships as first-class records, traversed with Cypher over Bolt and HTTP.Read about Neo4j →
- CouchDBDocument database with sync built in: JSON over HTTP, and replication that lets PouchDB and mobile apps work offline.Read about CouchDB →
- QdrantVector database for embeddings: similarity search, recommendations and retrieval for AI apps, over HTTP and gRPC.Read about Qdrant →
- WeaviateVector database with hybrid search: similarity, keyword and filtered queries over your objects, over HTTP, GraphQL and gRPC.Read about Weaviate →
- ChromaThe vector store most RAG tutorials start on, behind the API the chromadb clients already speak.Read about Chroma →
02Caching
Caching
In-memory stores for sessions, caches and queues, sized by memory and bound to your apps in one click.
- RedisIn-memory store for caching, sessions and queues. Runs Valkey, speaks the Redis protocol, as a cache or as a durable instance.Read about Redis →
- MemcachedThe simplest cache there is: a flat in-memory key-value store with no persistence, which is what Django, Rails, Laravel and PHP sessions expect.Read about Memcached →
03Search
Search
Full-text and search-as-you-type engines, from a single small process to an OpenSearch node.
- OpenSearchFull-text search and analytics over your data: the Apache-licensed fork of Elasticsearch.Read about OpenSearch →
- TypesenseTypo-tolerant, faceted search-as-you-type from one process that keeps the whole index in memory.Read about Typesense →
- MeilisearchSearch-as-you-type for your product: typo-tolerant, ranked, faceted results in milliseconds from a single small process.Read about Meilisearch →
04Messaging
Messaging
Brokers, streams and real-time channels, each speaking the protocol its clients already use.
- RabbitMQMessage broker speaking AMQP 0-9-1, so Celery, Bull, Sidekiq and Spring AMQP connect unchanged, with the management UI.Read about RabbitMQ →
- NATSMessage queue and streaming for background jobs and events, with JetStream so messages survive a restart.Read about NATS →
- KafkaEvent streaming with partitioned, replayable topics, managed by Strimzi, so every Kafka client connects unchanged.Read about Kafka →
- MQTT brokerMQTT 3.1.1 and 5.0 over TCP and WebSocket for devices, mobile apps and anything publishing over an unreliable link. Runs EMQX.Read about MQTT broker →
- CentrifugoReal-time messaging: clients hold a WebSocket or SSE connection, your backend publishes to channels over an HTTP API.Read about Centrifugo →
- SQS queueAn Amazon SQS-compatible queue on your own cluster, so code written for SQS runs unchanged against an endpoint you own.Read about SQS queue →
05Storage
Storage
S3-compatible object storage on the cluster itself, so backups and files need no cloud account.
- Object storageS3-compatible object storage on your own cluster, so database backups and files have somewhere to go without a cloud account.Read about Object storage →
- SFTP serverAn SFTP server for the files your partners, customers and apps exchange, with a web client and an admin API.Read about SFTP server →
06Observability
Observability
Metrics, logs and traces for every app on the cluster, and the console rewires itself to read them.
07AI
AI
Open-weight language models on your own hardware, behind the API your SDKs already speak.
- OllamaOpen-weight language models on your own hardware, behind the API every Ollama client and most OpenAI-compatible SDKs speak.Read about Ollama →
- Speech to textTranscription, translation and text-to-speech behind the OpenAI audio API, on your own hardware.Read about Speech to text →
- Text embeddingsEmbeddings and reranking for search and RAG, from any compatible Hugging Face model, behind the OpenAI embeddings API.Read about Text embeddings →
08Development
Development
Tooling for staging projects, so a test cannot reach a real customer.
- Mail catcherCatches every email a staging app tries to send and shows it in a web inbox, so a test signup cannot email a real customer.Read about Mail catcher →
- Headless browserA Chromium your apps drive over the DevTools Protocol, for scraping, screenshots, PDFs and end-to-end tests.Read about Headless browser →
09Build
Build
Your CI's jobs on your own cluster, beside the builds Anyport already runs there.
- Container registryA container registry on your own cluster: builds push there, apps pull from there, and your images never go to a third-party registry.Read about Container registry →
- GitHub Actions runnersSelf-hosted GitHub Actions runners on your own cluster, one fresh pod per job, scaled by GitHub's Actions Runner Controller.Read about GitHub Actions runners →
Need one that is not here?
The catalog keeps growing, and the next entries are chosen from what people ask for. Anything that runs as a container already deploys as an app, with its own volume and domain; a catalog entry adds generated credentials, binding, and the options above.