🏰 Fortress Launches: Manage Isolated Customer Databases in your Own Cloud

Fortress recently launched!

‍

^{"Databases for Multitenant SaaS"}

‍

^{TL;DR: 🏰 Fortress is an orchestration platform for SaaS applications, allowing them to easily manage a multi-instance database architecture (a hybrid of dedicated and shared instances) in their own cloud. If you are a SaaS using (or migrating to) AWS/GCP/Azure for databases, schedule a meeting!}

‍

‍Founded by David Chu, John Finberg & Will Hopkins -- recent Brown CS grads + open-source wiz.
‍

🚩 Problem:

As a SaaS grows, they follow these two trends:

1. They mature off 3rd party managed database platforms and move into their own cloud (onto an AWS/GCP/Azure) for cost, latency, and more control of their data.
2. They move from a single shared database architecture to a multi-instance database architecture for performance, compliance, and due to data isolation requirements of enterprise.

These result in headaches for SaaS startups.

Existing cloud-native database services not only have complex docs and SDKs, but orchestrating separate database instances requires additional DevOps: deployments, schema migrations, connection pooling, versioning across instances, etc.

‍

🏰 Introducing… Fortress

A database orchestrator that simplifies DevOps of managing a multi-instance database architecture on your private cloud.‍

‍

• ☁️ In your own cloud: Host your database instances in your own cloud for security and reduced vendor lock-in (and use your cloud credits!). They also have a fully-managed service!
• 🛠️ Simplified DevOps: Global schema migrations and rollbacks, versioning, and managed connection routing
• 👥 Tenant Management: APIs/SDKs to support easy provisioning of a dedicated instance for larger enterprise clients and easily add smaller clients to shared instances.
• ✨ Developer-friendliness: Easy-to-use client SDKs and ORM integrations. CLI and UI for admin.
• 🚀 Flexible Deployment: Deploy the database instance closer to your customer or to a specific region for compliance or reduced latency.
• 🔒 Security: Managed network isolation, custom Role-based Access Control for each database, encryption in transit and at rest, by default, simplified compliance audits, and easy tenant data deletion.
• 🧤 White glove migration: For now, they will do white glove migration to their platform (it’s fairly simple if you already use AWS/Azure/GCP for databases)

‍

‍

‍

Easily manage tenants, see their estimated usage, and what databases their data is in

‍

‍

Group databases by schemas to propagate schema migrations across groups (they handle rollbacks)

‍

🌟 Future plans?

• Schema Branching (branch current schema states and or freeze them for development)
• Zero-downtime schema migrations
• Experimental: Storage-compute separation to allow scaling to near 0 with Postgres in your own cloud

‍

❓ Ask:

1. If you work with customers who require dedicated db instances, chat with them! They'd like to learn more about your experiences with DevOps.
2. Let them know if you know any CIOs and CISOs! They'd love to chat!
3. Try their early access? It's easy to set up if you use a cloud-native managed service!

‍

‍

Learn More

^{🌐 Visit fortress.build to learn more.}

^‍‍

^{💬 If you work with customers who require dedicated db instances, chat with them! They'd like to learn more about your experiences with DevOps.}

‍

^{🤝 Let them know if you know any CIOs and CISOs! They'd love to chat!}

‍

^{‍🌱 Try their early access! It's easy to set up if you use a cloud-native managed service!}

^{‍
🌟 Give them a star on Github}

^{‍‍‍
👣 Follow Fortress on LinkedIn & X}