diff --git a/content/blog/20200918_splitgraph-matomo-elasticsearch-metabase.mdx b/content/blog/20200918_splitgraph-matomo-elasticsearch-metabase.mdx
index 7e5653d3..0d80bcc9 100644
--- a/content/blog/20200918_splitgraph-matomo-elasticsearch-metabase.mdx
+++ b/content/blog/20200918_splitgraph-matomo-elasticsearch-metabase.mdx
@@ -288,6 +288,6 @@ Metabase didn't care that these tables were actually views on other views on for
 
 In this post, we talked about our analytics setup that involves Metabase, Splitgraph itself and multiple backend data sources that we query through PostgreSQL foreign data wrappers. We discussed how it can provide business insights without adding extra complexity.
 
-On [our GitHub](https://github.com/splitgraph/splitgraph/tree/master/examples/cross-db-analytics), you'll find a sample setup that will let you query Matomo data from PostgreSQL.
+On [our GitHub](https://github.com/splitgraph/splitgraph/tree/master/examples/cross-db-analytics), you'll find a sample Docker Compose stack and configuration files that will let you query Matomo data from PostgreSQL.
 
-If you're interested in learning more about Splitgraph, feel free to check our our [website](https://www.splitgraph.com/)!
\ No newline at end of file
+If you want a similar setup, [get in touch](mailto:support@splitgraph.com) — [our private cloud program](/about/company/private-cloud-beta) is in early beta. It will let you set up own private Splitgraph cluster, managed by us and deployed to the cloud region of your choice.
\ No newline at end of file