Live data from Hacker News

Ask HN: Main things to consider when building an app for business/enterprise?

news.ycombinator.com

61–70 of 132 posts

Re: Ask HN: Main things to consider when building an app for business/enterprise?

#63

I was heading tech and product of a SAAS software for ~15 months so writing this from that experience. - Who is the buyer? Typically they are not same as the user of the product so understand what they look for in similar products. - SSO, preferably SAML based. - As for security, take care of OWASP top-10 [1] and you should be covered for app-sec. - Implement RBAC. Make it easy to add/manage users for an admin-user.…

Some great points there. I would also add a way for business users or admins to easily review accounts and privileges and sign off on that review if you are targeting any kind of regulated industry.

Re: Ask HN: Main things to consider when building an app for business/enterprise?

#64
post #53

I was heading tech and product of a SAAS software for ~15 months so writing this from that experience. - Who is the buyer? Typically they are not same as the user of the product so understand what they look for in similar products. - SSO, preferably SAML based. - As for security, take care of OWASP top-10 [1] and you should be covered for app-sec. - Implement RBAC. Make it easy to add/manage users for an admin-user.…

Background: cofounded an enterprise saas company. I like this coverage of tech, though it's missing soc2 which will be required. And 27001 eventually. I disagree on making it easy for admins to add users. Just don't: rather, implement (a bit of) scim or jit user creation with the idp flows. The big thing it's missing is sales. This software is sold not bought. In any sales process with 3 different constituencies (use…

When would you prioritise SOC2 before ISO27001? And when the other way around?

Re: Ask HN: Main things to consider when building an app for business/enterprise?

#65
Hi there, I just wrote about it here: https://silvertaza.com/product-market-fit/

I am sure that at the very least you'll get some ideas on how to approach this. I have aggregated different sources on that, but I am not an expert myself at this point in time.

Re: Ask HN: Main things to consider when building an app for business/enterprise?

#66

Earlier quoted context omitted.

As an alternative, if you containerize everything in the stack, you can simply spool up another seperate and isolated stack of containers for each given customer. Then it's also trivial if they want it 'on premise' somewhere or 'in the cloud'. No need to try and add complexity at the schema level and make a monolith support multiple tenants. Also, this list is quite literally supabase ( https://supabase.com/ ) - I ca…

This is absolutely the worse idea possible. I would never base my business on a technology that’s not widely used.

[deleted]

Re: Ask HN: Main things to consider when building an app for business/enterprise?

#67

Earlier quoted context omitted.

As an alternative, if you containerize everything in the stack, you can simply spool up another seperate and isolated stack of containers for each given customer. Then it's also trivial if they want it 'on premise' somewhere or 'in the cloud'. No need to try and add complexity at the schema level and make a monolith support multiple tenants. Also, this list is quite literally supabase ( https://supabase.com/ ) - I ca…

This is absolutely the worse idea possible. I would never base my business on a technology that’s not widely used.

While supabase could be considered a "technology" it's really more or less fancy wrappers around a postgres database. And even then, the wrappers it uses are rather well known:

- gotrue for auth, 3.2K GitHub stars

- postgREST to expost postgres as REST API, 19.8K GitHub stars

- kong as API gateway, 33.7K GitHub stars

Re: Ask HN: Main things to consider when building an app for business/enterprise?

#69
post #34

Earlier quoted context omitted.

If you're SaaS, enterprise doesn't necessarily care what database you're using -- and some of them may be a polyglot even internally. (My dayjob is a SaaS that's old enough to have started on Oracle in part because we thought it would make us look "serious" to enterprise clients, which include some fairly large financial institutions. We just finally turned off the last Oracle server, after switching to Postgres; no…

Yes that's true. But please consider that some orgs prefer self hosting their software. In this case using their database would be preferable.

In that case, only using ANSI SQL will help (i.e. no vendor-specific queries).
Post reply on HN