Blomstra, development services & scalable managed Flarum: Page 4

Blomstra, development services & scalable managed Flarum

luceos

We've received feedback from our first customer (mentioned luceos), @Fantomen of https://hockeybulletin.se wrote:

Incredibly hands on staff ready to spend hours helping out even though my community is comparably small.

In the future the absolute best hassle free solution for hosting a somewhat busy community.

Finally, the on boarding process was incredibly smooth with virtually no down time at all for my community; perhaps the most important aspect when changing the home for your community.

This recommendation will soon find its way onto our website. We are very close on sending out the lifetime discounts to the waiting list users, I'm stoked to hear what everyone else thinks once we are fully open for business!

luceos

A quick update from our end. We have decided to revisit a part of our stack based on the experiences with our early access communities. This includes the mysql database and the redis database. Once these two portions of the stack have been streamlined we plan to open up to the wider public.

In addition we are currently preparing our platform for the stable release.

My apologies for the delays to whomever was waiting on us, but we'd rather take our time to deliver great results than cause disappointment further down the line.

Desireamaze

seems too costly if changed on user cout basis

luceos

Desireamaze not sure what exactly seems costly. The active users mentioned are concurrent users (excluding bots). The lowest plan is perfectly suitable for many entry level communities up to 50 members/guests who are simultaneously online (and that's even a soft limit).

Also understand we do not attempt to undercut price fighting alternatives. That market is overly saturated. We provide a quality hosting experience for Flarum based communities.

Desireamaze

luceos I am looking for someone who could install, confugure, and secure a site based on Flarum for my specific needs where several hundred users might be ther at a time and hence said its quite costly. I also notice freeflarum and its really amazing but unable to user it on my own doamin as it only supports subdomain 🙁

Ayways, do you think you could help me launch my own site for specific purpose or would you like to recommend someone who coudld do it?

Thanks

luceos

Desireamaze I and Blomstra, do not provide installation services. You opened a discussion already, best is to wait for an answer there.

Desireamaze

Sure thanks

matteocontrini

I agree it might seem costly but if you consider what's included (storage, email, etc.) and that it's a managed service, it's actually on point. It's not too far from what you would spend by self-hosting it with a decent setup ("man-time" excluded).

Certainly the price for the entry-level plan is not that affordable but I can understand why 🙂

luceos

matteocontrini I agree it might seem costly but if you consider what's included (storage, email, etc.) and that it's a managed service, it's actually on point. It's not too far from what you would spend by self-hosting it with a decent setup ("man-time" excluded).

Yeah, it's fully scalable too and managed. No need to do complication migrations when you grow, implement your queues or scheduled tasks or switch over to a different websocket solution; we all got that covered. However we still recommend (especially larger) clients to configure their own email provider for sending because we still don't have the manpower to guarantee the best IP rating yet. Fighting spamlists is a fulltime job honestly. And defaulting to a third party service would bump the price unnecessarily.

matteocontrini Certainly the price for the entry-level plan is not that affordable but I can understand why

Lower plans will be considered later on when we matured the platform enough. Introducing those at affordable levels would require modulations to the stack that we'd rather not introduce right now.

luceos

Early June the platform we had was running smoothly, but was utterly destroyed due to the unexpected inability of Linode to scale our kubernetes control plane. The downtime caused due to this was disastrous and something we decided to ingrain into our vision for the future to prohibit from happening again.

That is why we are currently switching over to the Google Kubernetes Engine. Google has been fundamental in creating, maintaining and supporting kubernetes as an open source project. Their cloud is exceeding excellence and as such makes a perfect fit to the ambition of Blomstra to provide quality managed Flarum communities. Work is required from our end to move over, but we're already well on our way to go into an open beta later this year.

My apologies to all of you we have kept waiting, but we prefer to provide the services at a level you appreciate.

As a consequence we modified our timeline and decided to bring forward another plan we hoped to have started later next year. Starting today Blomstra is providing Flarum development, this includes commissioned extensions but also customisations in terms of design and layout. We will also be available for any Flarum related consultancy. Yours truly and @ianm will be your contacts for any of these assignments, unified under the Blomstra name.

matteocontrini

luceos interesting, could you perhaps share what happened with scaling on Linode?

Also, is there a particular reason why you're avoiding AWS? 😆 I've heard mixed opinions about GCP.

anonymousDev

Wait a minute @luceos
Plans from 49 euro/month? Simultanous users limit in XXI century? Seriously?
What is Managed email sending?

Taking users limit into consideration, Focus on your community growth ( from your motto ) sounds like rather sad joke.......

Its cheaper to spin-up new ( high-end ) AWS instance, pay upfront for 1 year and install Flarum manually.........

One must be crazy to pay you for hosting @ Blomstra.

Edit:

Seems it's pretty hard reporting back here while you're very busy making things move forward 😃

Well, if you find reporting back here hard ( due to time constraints / amount of work / wwhatever ) than why not focus on one projet only? Flarum was first. So, either Flarum ( here ) or Blomstra. Especially when you say sth like this:

luceos Will take a look within the next hours.

And these hours turns out to be one month........ Not very good move both credibility-wise and business-wise; if you say sth, stick o it no matter what. Or, say nothing and do whatever.

luceos Google Kubernetes Engine

I would not trust anything from Google when it comes to business solutions..........

luceos

matteocontrini could you perhaps share what happened with scaling on Linode?

Their kubernetes control plane is not set up to scale automatically. They already deployed changes to do so, but haven't enabled them. The inability to scale the control plane caused it to crash. Without the control plane our cluster had no way to scale up or down nor execute scheduled tasks or recover failing services.

They are also working on highly available control planes, but that is expected somewhere at the end of the year. Until then we will not consider them as a sensible partner in our stack, even though they are a lovely group of people to work with.

matteocontrini is there a particular reason why you're avoiding AWS?

First and foremost, Google is known to be excellent with kubernetes. Secondly a mate of mine has worked for all three major cloud providers and recommends Google above all others. I have heard how the AWS stack is set up and I can't say I follow their conventions.

Hari What is the meaning of the word "blomstra" ?

Blomstra means "to flourish" or "fare well", I used a translator to translate "blooming" into Icelandic, that's also why we choose the iconic Icelandic flower saxifraga stellaris as a basis to our logo.

luceos

matteocontrini I have to add that there are some additional factors at play. Linode is a centralised company in the United States, this event happened during a national holiday. Knowledge about k8s wasn't readily available to the support agents and escalation took ages. Our team has a ton of knowledge about kubernetes and would have been able to cooperate with their kubernetes team to get the issues resolved in a timely manner, but we were kept in the dark for hours on end. I'm glad that our feedback was welcomed by them, and for our corporate applications we will remain to use them.

Hari

What is the meaning of the word "blomstra" ?

matteocontrini

luceos I see, however technical support with GCP is not free and bandwidth is much more costly. Do you think it could affect pricing plans?

kemot

luceos

Wow, you have been through a lot already! Linode>GCP>now Azure.

Have you considered building your own kubernetes cluster? It seems that managed kubernetes offerings are still not up to the task. I hope that Azure will be good though!

luceos

matteocontrini yes, there's a chance our plans might need to be revised. We do hope it won't be necessary though.

luceos

I've posted an update about the state of Blomstra on our Greenhouse community. To sum it up:

New outage on one community due to issues on the Linode Kubernetes platform, which was resolved too slowly for our liking.
Google Kubernetes Engine held our initial hope, but their quota logic is overly convoluted and increases take too long.
We are currently working to migrate towards Microsoft Azure, which has been a joy to work with in terms of response from their staff, as well as their technical offerings.

All these setbacks has postponed our public beta, we're hoping to open up in the last quarter this year.

https://blomstra.community/d/60-platform-changes-2021-q3

luceos

Today the Blomstra Greenhouse community was migrated off of Linode to Microsoft Azure. Next up is moving closed beta customers as well. Once that is completed we will be revisit our pricing, optimize the stack further and prepare for the open beta.

In the meantime we made some huge progress on supporting Extiverse's latest feature, private premium extensions. Extension developers can publish premium extensions onto Extiverse visible only to subscribing clients. @glowingblue for instance is already using this functionality for some of their clients. For us, at Blomstra, it made sense to do our best to offer similar functionality on our platform. @ianm and I reworked the code responsible for the interaction with Extiverse and we're proud to say that our platform now fully supports private premium extensions as well.

« Previous Page Next Page »