Brixly - Cloud and Reseller Hosting Reviews 

Reply from Brixly - Cloud and Reseller Hosting

Nov 17, 2025

Dennis Nind here – founder of Brixly and now CXO.

I'm sorry you feel we've communicated poorly about pricing. That's something we've always tried to be transparent about, so it's disappointing to hear we've missed the mark with you.

Just to clarify what's happened: since the Enix acquisition, we've actually not made any pricing changes at all. The only increases that did happen were before the acquisition, and those were communicated through our usual channels – email notifications and our changelog. Those increases were directly tied to our upstream vendor costs going up, and even then, we absorbed a fair chunk of those increases ourselves (which we're still doing today, to be honest).

That said, if you didn't receive those communications or they weren't clear enough, that's on us. We should be doing better at making sure everyone's in the loop.

I'd be keen to understand more about what happened in your case. If you're willing, could you open a ticket with our sales team and ask them to forward it to me? I'll have a look at your account and see if there's something we've missed or could have done differently.

Thanks for the feedback – even the tough stuff helps us improve.

Cheers,
Dennis

Reply from Brixly - Cloud and Reseller Hosting

Nov 17, 2025

Dennis Nind here – I founded Brixly and I'm now CXO.

I'm really sorry you experienced those email issues. Email going down is incredibly disruptive, and I completely understand your frustration.

Based on when you left this review, I suspect this coincided with us rolling out our new in-house email gateway, Enmail, which replaced our previous provider. I'll be honest with you: the early days were rough. We had some teething problems with abusive senders that led to IP blacklisting issues, which would have caused exactly the sort of problems you experienced.

We've since resolved those issues completely and added over 2,000 additional relay IP addresses to the gateway. The solution is now performing brilliantly – we're seeing delivery rates that actually exceed what we had with our previous provider, and we're successfully delivering tens of thousands of emails daily with solid reliability.

I know that doesn't help with what you went through at the time, but I wanted you to know we've taken it seriously and sorted it out.

If you'd like to discuss what happened or if there's anything we can do to make it right, please open a ticket with our sales team and ask them to forward it to me directly. I'll look into it personally.

Warm regards,
Dennis

Reply from Brixly - Cloud and Reseller Hosting

Nov 18, 2025

Dennis here – I'm still very much involved with Brixly as CXO, and I've just seen your review.

I'm genuinely sorry to hear about the issues you were experiencing back in April. Websites going offline intermittently and then waiting over 24 hours for a response to a high priority ticket – that's simply not acceptable, and I understand completely why you were frustrated.

Just to clarify on the 24/7 support – our technical support has always been available around the clock, seven days a week. However, our sales and billing teams do work UK business hours, which may have caused some confusion if your ticket went to the wrong department initially. Either way, a high priority ticket should never have waited that long for a response.

Since April, we've made significant improvements to our support. We're now averaging response times of under 30 minutes, and we've introduced live chat for all customers with typical response times under 4 minutes. We've also been working hard to address the reliability issues that were causing intermittent downtime.

I haven't gone anywhere – I'm still here, and I still care deeply about getting this right. If you're still experiencing any issues now, or if there are ongoing concerns from back then that weren't properly resolved, I'd really like to look into it personally. Please open a ticket with our sales team and ask them to forward it to me directly, and I'll make sure we get everything sorted.

Best,
Dennis

Reply from Brixly - Cloud and Reseller Hosting

Nov 18, 2025

Dennis Nind here – founder of Brixly and now CXO.

I'm sorry to hear you've had such a poor experience with us. Loading times of 40-50 seconds and the other issues you've described are clearly unacceptable, and I can understand your frustration.

I do want to address a few of your points, though. We actively monitor all our servers with live WordPress sites, and our average loading times for completely uncached websites are consistently sub-1 second – typically around 500ms or less. Loading times of 40-50 seconds suggest something specific going on with your account, such as resource consumption issues or a particular configuration problem, rather than a systemic server overload.
That's still our responsibility to identify and fix, but it's not something that should be affecting all customers.

Regarding email, you're right that we built our own gateway – Enmail – to replace our previous provider. The early rollout was admittedly rocky, with some IP blacklisting issues that we had to work through. However, we've since resolved those problems completely and added over 2,000 additional relay IP addresses. The gateway now consistently delivers tens of thousands of emails daily with delivery rates that actually exceed what we saw previously, and with solid reliability.

On support response times – we've made significant improvements since the challenges during the transition period. We're now averaging under 30 minutes on tickets, and we've introduced live chat with typical response times under 4 minutes.

That said, none of this helps if you were experiencing these issues and didn't get them properly resolved. I'd genuinely like to look into what happened with your account. If you're willing, please open a ticket with our sales team and ask them to forward it to me directly. I'll investigate personally and see what went wrong.

Best,
DennisRetryClaude can make mistakes. Please double-check responses.