[danpalmer]

I've looked at IHP briefly a number of times and the thing that always turns me off it is the fact that it's perhaps _too_ batteries included.

When I read the pricing page on IHP's site, and see something like "Email confirmation" (for authentication) having a price associated with it, it makes me assume that IHP is sufficiently locked down that I couldn't just build that feature myself. Either it's not, and I can do, and I've got the wrong impression, or it is, and I worry that IHP having that much control over my codebase will make other things that it doesn't support much harder than with other frameworks.

I'm all for the business model of well integrated, well supported plugins for the framework, but a closed, tightly controlled development environment that I can't break out of as I feel is necessary isn't something I'd bet a company on.

[_query]

Thanks for the feedback!

Check out the docs for email confirmation here: https://ihp.digitallyinduced.com/Guide/authentication.html#e... You'll see that most parts of the confirmation workflow actually happen inside your application. Only the actual controller implementation is part of IHP pro, and it's just 20 lines of code. So you can easy implement this yourself.

Generally IHP uses a lot of standard libraries of the Haskell ecosystem. So you can always break out of IHP when things don't work. It's not much more lock in than other frameworks in the space :)

Some more background on the ideas behind the pricing can be found here btw: https://ihp.digitallyinduced.com/Guide/ihp-pro.html

[nextaccountic]

I don't understand how can you make MySQL support and role-based access control paid features. Are they not open source?

[_query]

Yes, the paid features are part of a closed source fork of IHP

[danpalmer]

Thanks, that does address my concerns well.