Salesforce Technical Architect · Creator of Salesforce Binge
crmarcade is a curated directory of tools, frameworks, and resources for the Salesforce ecosystem. Every entry is handpicked — tools I’ve used on real projects, or evaluated closely enough to have an opinion on. No sponsored listings, no filler.
Why “crmarcade”?
The Salesforce ecosystem has thousands of tools scattered across GitHub, AppExchange, and blog posts. Finding the right one for a specific problem — especially one that’s production-ready and architect-approved — shouldn’t require hours of research. crmarcade is the directory I wish I had when I started building on the platform.
But tools are the starting point, not the destination. An architect doesn’t just need a good data migration utility — they need to know how it fits into a high-volume migration strategy with staging orgs, bulk API limits, and rollback planning. That’s where crmarcade is heading.
Today, the directory gives you the toolkit. Tomorrow, it will pair those tools with architecture scenarios — real-world patterns like enterprise SSO across multiple orgs, large-scale data migrations, or document generation at scale. The kind of problems CTA candidates study and working architects solve every quarter.
The name “crmarcade” is intentional. We start with Salesforce — the ecosystem I know best. But architects rarely work in a single platform. Migrations from legacy CRMs, multi-platform integrations, hybrid landscapes — these are real scenarios. As the directory grows, so will its scope. The “arcade” is the collection, and the collection grows with experience.
How Tools Are Selected
Every tool in this directory meets at least one of these criteria:
- Battle-tested — used in real enterprise implementations
- Well-maintained — active development, responsive maintainers
- Solves a real problem — not a toy or proof-of-concept
- Architect-relevant — useful at the solution design level, not just quick fixes
Suggest a Tool
Know a tool that belongs here? Submit a suggestion with the tool name, URL, category, and why it matters.