---
title: "Why Trainy migrated from Amazon RDS Postgres to ClickHouse Managed Postgres"
description: "Trainy’s Pluto is an open-source experiment tracker that separates analytics metrics in ClickHouse Cloud from relational run metadata in Postgres. Its original metadata store, Amazon RDS Postgres, was too expensive for the volume observed and contributed to slower initial page loads, so Trainy migrated roughly 40–50 GB to ClickHouse Managed Postgres, which uses local NVMe storage and keeps both databases in one account. After migration, initial page loads became 2–3 times faster, while a complex query reported as taking 10–15 minutes previously returned in five seconds; visualization queries over runs with hundreds of thousands of steps typically return in 50–100 milliseconds at the P50. Trainy reports 100% reliable ingestion with zero dropped data points and says the unified stack could support future joins between GPU metrics and run metadata, as well as governed agent access."
---

# Why Trainy migrated from Amazon RDS Postgres to ClickHouse Managed Postgres

[Clickhouse](https://yomu.fyi/company/clickhouse) · Jul 15, 2026

**Type:** Problem & solution

## Summary

Trainy’s Pluto is an open-source experiment tracker that separates analytics metrics in ClickHouse Cloud from relational run metadata in Postgres. Its original metadata store, Amazon RDS Postgres, was too expensive for the volume observed and contributed to slower initial page loads, so Trainy migrated roughly 40–50 GB to ClickHouse Managed Postgres, which uses local NVMe storage and keeps both databases in one account. After migration, initial page loads became 2–3 times faster, while a complex query reported as taking 10–15 minutes previously returned in five seconds; visualization queries over runs with hundreds of thousands of steps typically return in 50–100 milliseconds at the P50. Trainy reports 100% reliable ingestion with zero dropped data points and says the unified stack could support future joins between GPU metrics and run metadata, as well as governed agent access.

## Context

Pluto’s metadata layer on Amazon RDS Postgres had two explicit problems: its initial defaults were too expensive for the volume Trainy was seeing, and fetching experiment metadata contributed to slower initial page loads. Trainy also wanted to keep its analytics and relational data services within the same ClickHouse account and vendor.

## Approach / What changed

Trainy moved Pluto’s approximately 40–50 GB metadata layer from Amazon RDS Postgres to ClickHouse Managed Postgres while retaining metrics and analytics in ClickHouse Cloud. The managed Postgres service uses local NVMe storage, and the combined setup keeps the OLAP and OLTP databases under one account. Trainy is also considering CDC replication and governed agent access for future cross-database workflows.

## Takeaways

- Pluto places observability-style metrics in ClickHouse and relational run data, including creation times and hyperparameters, in Postgres.
- ClickHouse Managed Postgres runs on local NVMe storage rather than the network-attached storage used by most managed Postgres services, keeping storage next to compute.
- ClickHouse query insights give Trainy 80–90% of the way toward identifying whether slow queries originate in application services or query optimization.

**Tags:** [AWS](https://yomu.fyi/topic/aws), [Migrations](https://yomu.fyi/topic/migration), [Observability](https://yomu.fyi/topic/observability), [Performance](https://yomu.fyi/topic/performance), [Postgres](https://yomu.fyi/topic/postgres)

- Source: [Clickhouse](https://clickhouse.com/blog/trainy-postgres-managed-by-clickhouse)
- Source URL: https://clickhouse.com/blog/trainy-postgres-managed-by-clickhouse
- Ingested by Yomu: 2026-08-29T01:38:45.967Z

[Read original post](https://clickhouse.com/blog/trainy-postgres-managed-by-clickhouse)