The data is stored on the platform itself through something called a "store" service. In the long term we'll offer exporting that or backing by your own data storage if that's preferable. Micro provides built in primitives for auth, config, storage, etc. You can learn more about them here https://micro.mu

It's open source and you can self host it yourself if you want. Micro also provides a full development model for services development, since it's also a framework and not "just" a platform. Disclosure: I'm a contributor.

Good question. Cloudflare and many other platforms like it are closed source and you're mostly locked in to a very custom development model, there's also no escape hatch. For what you get, it's great, I love cloudflare but I also think we're in a world where being open source first matters. Micro is open source (https://github.com/micro/micro) and that's how it started life. It's now "source available" in the sense that we use a license that stops AWS from picking up and hosting it for profit without contributing back, but it's otherwise completely usable for any purpose.

Micro as an open source platform enables the ability to self host, develop locally and move beyond our offering m3o.com. I think it also creates trust and thats something we're going to really be thinking about a lot in the next 5-10 years.

We're also looking beyond the core primitives themselves towards these value add services in the category of "backend", "logistics", etc. I think providing a generic platform as a service isn't good enough anymore, we really have to push a lot further.

I think Dapr has the same goals as Micro. Dapr is from the team who built Azure Service Fabric, which is basically a microservices platform, and with this they've decided to take an open source angle for kubernetes. We're going the other way. Open source is great, but it's not enough. Micro 3.0 is a hosted platform and focused on removing that operation burden but also providing value add higher level services.

I think like most things you either prefer dapr's primitives or ours. As was the same with go-micro vs grpc-go.

Micro can be self hosted. It's an open source project for which you can find the docs here https://micro.mu.

Yea good question. Micro started with the domain micro.mu for the open source project and we recently found m3o works as a nice moniker and were able to get the dotcom so I think for searchability its "m3o" but the name is Micro, that's what we've always been since inception. And yea Go users search for Golang :) so Micro users search for m3o.

Here you go https://docs.m3o.com/faq#fair-usage-policy