What do you like best about Superblocks?
It's not until you truly attempt a wide roll-out of an internal tooling platform that you understand the difference between an impressive demo and the reality of trying to integrate dozens of systems. Superblocks is engineered for an impressive balance of flexibility and ease of use which has supported our 3 person team in maintaining momentum of onboarding dozens of organizations with hundreds of users. This simply wouldn't be possible without Superblocks (believe me, we have tried!).
The design philosophy of Superblocks is fundamentally different to any other solution we have evaluated, owing to a deep understanding baked into the product of the practical challenges faced by medium-large organizations. Superblocks provides intergration points to solve for integration challenges at every level, setting it apart from competitors in the way that Auth0 did for AuthN/AuthZ. Other options we explored made too many assumptions about our business & tech, so be sure to bring your most frustrating use cases to your evaluations and you'll start to understand how Superblocks differentiates.
The barrier to building internal tools for our organization was our heterogeneous enterprise network architecture consisting of multi-cloud and on-premise networks relying on multiple VPNs to access our services. Superblocks has an on-premise agent which flexible deployment enabling us to onboard dozens of teams to develop internal tools without requiring traffic to traverse the internet. This is simply the current reality for many hyper-grown companies, so we love to find vendors who meet us where we're at without criticizing the maturity of our architecture.
Being able to inject code to almost any component of the tool provides an escape hatch for our users to bind to legacy or esoteric systems, often being able to port existing bindings across and without relying on Superblocks to prioritize and build custom product features for us. Support for workflows also means we're able to move asynchronous tasks and ETLs previously driven by opaque CI tools, providing the observability and reliability we need for our processes.
All of this is complemented by the Superblocks support team acting as an extension of our organization. The result is our teams being empowered to solve their own tooling gaps without having to undergo a vast multi-year modernization effort or sacrificing control and compliance. We have experienced even non-technical users being able to ramp up and author their own custom integrations using generative AI features, which is something which would be unimaginable before.
Superblocks is here as a partner for the long-haul of modernizing our business. The ROI was proven in weeks, not months, and this compounds as more users become familiar with using the tools and our users continue to organically drive down COGS in innovative ways we hadn't even considered before. Review collected by and hosted on G2.com.
What do you dislike about Superblocks?
Superblocks has focused on investment in flexibility of the tool authoring experience, which is the right prioritization call. Where it is lacking is support for enterprise features in their management console, such as support for custom domains, ability to create and manage multiple tenants mapped to organizational units, centralized policies to act as guardrails (in the way that AWS SCP works), and visibility into usage & billing. We've been able to build our own solutions for some of these (in Superblocks!) and custom domain support is somewhat mitigated by the new embedding feature. For the remaining gaps we've found the product team to be receptive to our feedback and are looking forward to seeing future iterations. Review collected by and hosted on G2.com.
