Hosting a company website on our own?

JCPhoenix
2024-02-03T10:30:55Z

Edit: I appreciate everyone's suggestions and recommendations! After speaking with my co-worker, I think we'll got with a Managed WordPress solution. Still have a lot more to discuss and figure out, but I suspect that'll at least put us on the right footing. Thanks!

Hello Tilderinos. I need your knowledge and advice.

The organization I work for wants to build a new website. Traditionally, we've used an AMS, which is an Association Management System. These are typically used by non-profits, which is what we are, a voluntary regulatory non-profit. It combines a CMS with a CRM in a proprietary package. It's also entirely hosted and managed by the AMS developer, which is typical for these platforms. Basically a turnkey solution.

We have a web designer/developer-yet-doesn't-want-wear-the-developer-mantle and me, who's really more of a desktop support/low level sysadmin for our small organization. I'm jack of all many trades, master of none.

Our web designer is really interested in either self-hosting WordPress or even looking into a headless CMS. He wants more creative and functional control over our website than what we currently with our AMS. We are very limited to what we can do right now, since we're playing in the AMS' sandbox with only some HTML/CSS and light JS use. Anyway, from there, we'd use API calls to query the new CRM that's currently being built out (it's a proprietary one, akin to Salesforce) to generate dynamic content.

I could go out and get webhosting at like a GoDaddy (I wouldn't use GoDaddy) or somewhere like that. I've done that before for some smaller auxiliary sites. Sites that, if they go down for a day or two, it's kinda NBD, while I try to figure out what's going on and reach out to the webhost for assistance. I literally just did that earlier this week on one of those sites.

But this would be our main website. And we have a global customer and stakeholder base. People are always on our website 24/7. I'm hesitant to commit to doing it this way because I feel like there's so much that would drop into our laps that we don't know how to handle. What happens when the site goes down for some reason? Is there a failover? How do I even set that up? How do we do backups and rollbacks? How about security issues? How do I harden the site and system? What happens if we do get hacked? We've discussed the issues with WordPress, which are many. How do we deal with all those issues on our own? I don't know the answer to any of these.

Like I said above, we don't have to deal with any of those questions right now. Our AMS provider deals with all that. I'm sure they have a team in a NOC or similar that watches the infrastructure 24/7. Part of what we pay them is so they can handle all that. No way in hell my co-worker and I are willing or able to do all that. And it's not that I'm not willing to learn how to do all this stuff, but to me, this seems like the wrong venue and time to be learning on the fly.

Idk. Are my concerns overblown? Is it really just as easy as getting some webhosting space somewhere and installing WP or some headless CMS and letting my web dev go to town? I know my co-worker could build the site out. I'm just not sure if I could support it all during and afterwards.

Any advice or suggestion would be appreciated. Because right now, him and I are going around in circles trying to figure this out, ha. Thanks.

Comments URL: https://tildes.net/~tech/1dy4/hosting_a_company_website_on_our_own

Votes: 17

Comments: 17