“We needed fast, programmatic provisioning of Postgres on Azure, support for pgvector and RAG, and something that could scale easily across tenants. Neon checked all those boxes” (Chris Sims, CEO and co-founder of Rhythmic)  

If you’ve ever worked in product management, you know the feeling. You want to spend more time talking to users, refining strategy, and shipping. Instead, You’re buried in status reports, backlog refinement, and internal updates. 

Rhythmic is here to change that. Their mission is simple: to build an AI for product people. The goal is to eliminate the repetitive work that holds product managers back, and make it easier for teams to focus on solving real customer problems.​​ Think of it like an AI copilot for product managers.

Free Your Product Team to Focus on Customers, Leave the Grind to AI

“The best products are built when humans get out of the office and interact with customers. We’re using AI to automate the busywork that gets in the way of that” (Chris Sims, CEO and co-founder of Rhythmic)  

The platform is currently in Early Access. Take a look at what they’re building: 

• Epic story builder. The platform includes a  conversational workflow that breaks down complex epics into fully-scoped user stories, complete with titles, descriptions, acceptance criteria, and initial complexity estimates.
• Automated backlog planning. From a single interview, Rhythmic knows how to generate release-ready backlog and prioritize stories. .
• Internal notes. The platform also generates summaries, meeting notes, and status updates to keep stakeholders aligned with minimal manual effort from the PM.
• Live sprint planning. If your team works in sprints, capacity-aware AI recommendations help you plan smarter sprints, balancing workload, adapting to shifting availability, and adjusting in real time.
• Proprietary estimation engine. Rhythmic’s VERA model learns from your team’s historical data to get better overtime.

Choosing Neon on Azure

“Postgres fits with our architecture, and Neon made it easy. I didn’t want to deal with any overhead, Neon worked out of the box and let us stay focused.” (Chris Sims, CEO and co-founder of Rhythmic)  

Rhythmic began as a fast-moving prototype built on Vercel and Trigger.dev. As they started preparing for enterprise customers, long-term stability and compliance became top priorities. That meant moving infrastructure to Azure.

But when it came to choosing a database, Rhythmic doubled down on Neon. Neon offered the best of both worlds: a great developer experience and a path to enterprise scale, without the maintenance burden of traditional managed Postgres. 

• Simple setup. Setting up a Neon project was trivial—quick, smooth, and didn’t require reworking their infrastructure.
• Fast provisioning. “If you’re doing agentic workflows or AI integrations, having Neon provision new databases quickly makes a huge difference”, said Chris. “We’re planning to give each agent or tenant their own project over time.” 
• Developer-first. Neon offered a modern dev experience that fit naturally into their stack.
• No infrastructure babysitting. Neon handled the operational complexity behind the scenes, liberating precious engineering time. As Chris put it: “Databases should be like plumbing: you want good plumbing, but you don’t really want to care how it works.”
• Enterprise-ready foundation. Via Neon’s tight integration into Azure, Rhythmic gets unified billing, Microsoft SSO support, and compatibility with Bicep, Terraform, and other tools their enterprise customers expect. 
• Built to scale with privacy in mind. Neon’s architecture opens the door to scale with per-tenant isolation through project-level provisioning, setting the stage for Rhythmic’s future plans to offer dedicated environments for each customer.

Making it Easy With the Neon Azure Native Integration

Rhythmic was already using Neon in their initial stack, on an non-Azure Neon tenant. After joining Microsoft for Startups and shifting to Azure for long-term compliance and partner alignment, Neon’s integration with the Azure ecosystem made the transition smooth. What stood out:

• One-click org creation in the Azure Portal 
• Unified billing and SSO (everything tied to their Azure subscription)
• Terraform, Bicep, and CLI support (their infrastructure-as-code workflows stayed intact)

As Rhythmic’s infrastructure grows more complex, these native integrations will become increasingly more valuable. Neon will continue to deepen its Azure support—we have items on our Azure Native roadmap from managed identities to observability.

“Getting started with Neon Azure Native Integration was trivial, which is exactly what you want. We clicked a few buttons, changed some keys, and everything just worked.” (Chris Sims, CEO and co-founder of Rhythmic)  

Building RAG in Postgres? Yes, with pgvector

Instead of reaching for a specialized vector database, Rhythmic is sticking with Postgres as their foundation for RAG. Their goal is to simplify the stack while keeping costs low and performance high, especially as they build toward multi-tenant AI deployments. Here’s what that looks like today:

• Postgres for both structured and vector data. Embeddings live right next to the rest of their product data.
• pgvector for semantic search. Easy to set up, performant, and flexible enough for their needs today.
• Planning for per-project database isolation. Rhythmic is starting with a single Neon database and partitioning by tenant, but their long-term plan is to give each customer a dedicated project and database. This will make their RAG and AI agent infrastructure easier to scale and secure.
• Avoiding Azure Cognitive Search. This is too expensive for a small team, especially in multi-tenant setups.

Try Neon on Azure and Start Building 

If you’re building on Azure, Neon’s Native Integration makes it easier than ever to get started. You get the same serverless Postgres experience loved by developers but with full Azure billing integration, support for Microsoft SSO, and eligibility toward your MACC. 

Spin up your first Neon project directly from the Azure Marketplace or the Azure Portal, and start building with serverless Postgres that scales with you.