Why We Moved Monk From Vercel/Supabase to AWS

We recently moved Monk's backend from Vercel and Supabase to AWS, for more control over reliability and performance, and full control over where our customers' financial data lives and is processed. This post covers what changed, why we did it, and what it means for the security of your data.

Why we made the move

As our platform has grown, we wanted to own our infrastructure end to end, so we can tune reliability and performance ourselves and decide exactly where customer data lives.

We moved the long-running side of that work onto a dedicated workflow engine earlier this year, which we wrote about in why we moved 100 workflows to Temporal. The next step was to move fully onto AWS, for more control over security, access, and infrastructure.

What changed

We moved compute and data to AWS. Our services run in containers, with application data in Aurora and S3, infrastructure defined in code so every change is reviewed and reproducible, and monitoring wired across the stack so we catch issues early.

This gives us two things:

• More direct control over how customer data is secured, isolated, and kept compliant, because it lives inside our own AWS environment.
• Room to scale as the product grows, without working around the limits of a platform built for a different kind of workload.

What this means for your data security

Owning our cloud environment gives us more direct control over how your data is protected. Every customer's data is scoped to their organization, access is role-based and reviewed, data is encrypted, and we hold to a defined retention policy, with production data never used in development or testing. Every action the platform takes lands on an audit trail you can inspect.

Our compliance posture

Monk is SOC 2 Type II, and we monitor those controls continuously rather than treating compliance as a once-a-year event. We are extending our program toward ISO 27001. Owning our environment also gives us room to keep hardening reliability and observability, and to keep raising our security standards as we grow.

Frequently asked questions

Why did Monk move from Vercel and Supabase to AWS?

For more control over reliability and performance, and to set ourselves up to scale into the next chapter of growth.

How is my data kept separate from other customers?

Each customer's data is scoped to its own organization, encrypted, and access-controlled, so one customer can never see another's, and every action is captured on an audit trail you can inspect.

Is Monk SOC 2 compliant?

Yes. Monk is SOC 2 Type II and monitors those controls continuously, and is extending its program toward ISO 27001.

Is my data used to train AI models?

No. Your data runs the agents that work your receivables. It is not used to train models.

Did the migration affect customers?

No customer action was required. Traffic moved over cleanly, with the change happening behind the scenes.