Neo4j community edition limitations (deep dive)

My target is to achieve MVP (minimum vaible product) with neo4j community edition and move for enterprise edition.
I'm good to deliver MVP with known limitation as 1 DB with cold backup,no rbac. However wondering what other limitation (transaction management, performance etc) I should be considering while moving from 30000 feet view to 3000 feet view of neo4j community edition.
Any help is greatly appreciated.

Performance is a big differentiator between Enterprise and Community,
The community edition uses the 'Slotted' Cypher runtime for execution, while the Enterprise edition uses the more advanced 'Pipelined' runtime.
As always, it depends on your data and use case, but on internal benchmarks, the Enterprise edition is about twice as fast as the Community edition.

In addition, the Enterprise edition offers the Parallel runtime, which allows individual read queries to be run in parallel across the server cores. This is particularly useful for analytical (long-running) queries and can significantly boost performance. Using the Parallel runtime, most read queries performance scale linearly with the number of available cores.

I don't know if this can be useful for your MVP, but the Neo4j AURA fully managed offering is based on Enteprise, it has a Free edition (pipelined runtime, but not parallel runtime), and the possibility of gradual upgrades from Free to Professional and then Enterprise tiers.

First of all, A big thanks to you @valerio.malenchino. Your inputs are grately appreciated. See cost is driving factor irrespective of how big or small project budget is. I'm trying to cover up all the corners possible to take an informed decision, how far can live with "Community edition" and put in production for adoption.