Internal’s new enterprise-ready app builder includes a flexible drag-and-drop UI to build tools, powerful dev tools to connect to any API, and robust security options including permissioned data flows and SOC 2 certified cloud or on-premise hosting.
Since the first product I worked on over a decade ago there was always one requirement that was the same between them: a need for an internal admin system. Whether it was Yammer (enterprise social network), Simple (banking), Vault (retirement investing), or Acorns (investing), we always had to dedicate some of engineering resources to building out an admin system.
If we didn't do this we'd get pulled off our product work to fix people's accounts, answer questions for the support team, or deploy our monolith just to update some copy.
When I found Internal.io I immediately signed up for my next startup. It let me integrate our GQL backend and database and, in one use case, even a Google Spreadsheet, and let our support and non-engineering team members manage everything themselves. I've ever since been preaching this to every CTO and VPE I talk to. I highly recommend!
@oscargodson thank you for your support! Our goal is to build out a powerful platform so engineering teams never have to worry about internal tools again!
@oscargodson Thanks for all the support... we really appreciate it. It's been great working with you on this and we're looking forward to saving you more time with your new endeavor.
@arisa_amano1 Is there a good comparison with Retool you'd recommend people look at? I'm doing a side by side right now and it looks like the pricing for basic use cases is double Retool, and Retool seems to have more components and deeper docs. But maybe I'm missing a key differentiator?
@imogennnmnnnnnn Great question! Internal is not an engineering tool. It's a platform that empowers non-coders. Of course, developers can use it as well and many of our users are in fact developers. However, with Internal, developers don't have to build/maintain everything end to end. Also, Internal provides end user mode + super granular permissions (not just app-level permissions but field level) at every tier including the free tier. We found that companies almost always need these features, even for basic use cases (unless they're just building a tool for themselves). Hope that helps!
@evanm1 Thanks! One of our priorities is a super fast setup. If you connect a database, you already have some things set up for you!
Report
We've been using Internal for about six months. Its flexibility has allowed us to quickly create some vital admin tools using some very sophisticated queries to our databases. I haven't found other solutions that are this useful.
The team has rapidly iterated and the experience of creating admin tools now is worlds better than it was when we started using Internal last summer.
I couldn't recommend it more!
@seungjun_jun_lee Great question! We think Retool is a great engineering tool. Internal, on the other hand, is a platform that empowers non-coders (teams like product management, customer support and ops - the people that depend on these tools every day to do their jobs). Developers can use it as well (and many of our users are in fact developers) but with Internal, developers don't have to build/maintain everything end to end. We think this approach is valuable, especially for companies that a) want to keep their developers focused on core products, and/or b) companies that just don't have enough engineers to support everything.
We've been using Internal and it's been saving us so much time by allowing us to build out internal customer support tools without engineering overhead. The Internal team has been very responsive and quick to resolve any bugs we found!
@tina_roh we're happy to hear that Internal has saved your team engineering time and that you've been able to build out your customer support tools on our platform!
@daryllman while anyone who needs to build internal tools connected to their existing systems can get a lot of value out of internal, our ideal customers tend to be customer support and operations teams who sometimes struggle to get enough engineering time to implement the tools they need. We're also finding a lot of interest from engineering teams that want to keep most of their attention focused on their user facing product, while still providing a polished experience for their internal teams.
This looks great! How do customers handle integrating Internal Enterprise's permissions with their own APIs? We have roles and permissions centralized in one of our codebases, and am wondering whether a tool like Internal Enterprise would wind up with these permissions being duplicated or split.
@chrstphrwrght Internal can integrate with your API's authorization mechanism (http basic, oauth or custom). In that case you can restrict data at the API level and Internal does not need to know about your system's roles and permissions; however, if you want to get more granular then you can by layering Internal's fine grained permissions. Happy to discuss further if you would like to schedule a call or a demo.
Report
I am a huge fan of Internal and their team. They have been an incredible partner for us in building no code tools for our team through periods of massive growth. I have not encountered another product like this on the market, and their solutions engineering approach to helping us solve problems and iterate fast has been exceptional.
Replies
Vault
Internal
Gleek
Ragie
Ragie
Internal
Internal
Ito
Internal
Internal
Internal
Ragie
WiFi Map
Internal
Every.org
Internal
Ragie
Ragie
Zodier
Ragie
Ragie
Internal