Being poached by Quave insistingly

[paulishca]

Hi @filipenevola I am glad you closed the loop. To be frank, those emails were pretty annoying. Man, if you don’t like Galaxy, don’t use it.
Anyway, I wanted to hear more about Galaxy. Why don’t you make your point here so we can all migrate out of it and rush like headless chickens to Quave…

"In many Meteor.js teams we talk to, the real bottleneck isn’t dev capacity, it’s infra. Especially around Galaxy setups, MongoDB Atlas costs, scaling issues or DevOps overload.

Alongside dev support, we also run Quave ONE, a provider-agnostic platform that helps teams migrate off Galaxy, optimize MongoDB costs, reduce infra spend and avoid lock-in."

Which teams did you talk to and how many is many?
What is the infra bottleneck in Galaxy?
What do you mean you plug devs into teams from $4.999?! Seriously, you heard about AI, did you? Where I live I can get an unforgettable plug for less than 50 bucks.

With the work and activity you had as CEO at Meteor, I am reluctant to even use anything written by Quave code or X posts. Did you notice that everything amazing in Meteor happened after you left? Well … I did.

Look, I don’t want to be rude, it is late in my place, I am at the end of a productive day, and I really needed some fun. But I’d suggest this… if you like Meteor, if you use Meteor, it would be nice and enough to just push some code. You really don’t have to go after their clients.
For the past years you turned this place into your own Marketplace, there is more “we at Quave” in the history of this forum than the word “Meteor” …
Anyway, if you ever decide not to write to me again or to stop poaching people here, I will not be upset. I will understand that it is your right to pursue business ethically. Your fundamental right.

[fredmaiaarantes]

@paulishca, thank you, really.

We’ve heard this before. Multiple people reported aggressive outreach from Quave directly to us. But I won’t get into how other companies run their business.

On the Meteor side: we rebuilt the team from scratch, and I’m genuinely proud of what a small group has been delivering. We’re catching up on years of missed ground, and the results have been better than the headcount would suggest.

Galaxy is part of that same push. We’re mid-migration to Galaxy Metal, a fully rebuilt infrastructure on bare metal and Kubernetes. Soon, people who left Galaxy years ago will have strong reasons to take another look.

And for the ones who want to support MeteorJS, there are many ways: code contributions, open issues, tests, PR review, share your stories. Running your app on Galaxy is another direct one.

There’s a lot more coming. Excited for v3.5 and v3.6!

[paulishca]

Here we go again…

@filipenevola man … talk to your team … It is enough … we “closed the loop” already …

[harry97]

I hope people in hindsight now can understand why I wasn’t pleased as how things have been transpiring before but let’s not focus on the past.

I’ve been in talks with @nachocodoner today and the sheer amount of work that’s been put lately into Meteor is nothing short of appalling:

• Fibers to async
• Old build system to Rspack @nachocodoner
• Oplog to changestreams (@italojs now gets the recognition he deserves and establishes himself as a solid core contributor)

Many new faces joining in to contribute to the core @dupontbertrand @mvogt22

Meteor has nothing but good things coming. Kudos to core team and Meteor Software @fredmaiaarantes

[marioperino]

Hey @paulishca , I’m Mario Perino. I recently joined Quave as CRO, so I’m the one responsible for setting up our outreach efforts, including the cadence and frequency of the messages you received. Rafael Rolim, who reached out to you on LinkedIn, works on my team.

If you felt bombarded, I appreciate the honest feedback and I’m sorry it came across that way. We’ll take it into account.

To grow Quave and reach the teams that could benefit from our services, we’ve been running sales outreach, and unfortunately part of that process means some messages will land with people who don’t have the pain we solve. For them, it’s just noise, and I get how that can be annoying. That’s exactly why every email we send includes an unsubscribe option that removes you from any ongoing sequence.

That said, for some teams we’ve been able to be useful. We work with Meteor teams that run into things like performance issues, scalability challenges, infrastructure costs, version migrations, DevOps bottlenecks or specific code questions. Some of them were dealing with real blockers, struggling to scale or even considering moving away from Meteor. When that happens, we roll up our sleeves and help them solve it. It’s rewarding to see those teams get past the blockers and keep growing their companies on Meteor.

If your team doesn’t have those issues and handles everything internally, that’s great. Meteor and Galaxy are solid technologies with real value, and we use Meteor heavily ourselves. We have a lot of respect for what the core team is shipping.

We need to get the word out to find the people who do have the pain. That means some outreach will miss the mark, and that’s part of the process. I hope that context helps explain where we’re coming from.

[paulishca]

Guys, reach less and push more code. This is what the rest of us are doing here …

[wreiske]

I got one too! I guess I’m on the list somewhere…

[harry97]

Why am I not getting one? Oh wait we’re already using Quave . Their MCP is amazing tbh, kudos @filipenevola . Galaxy need to implement it too!

[storyteller]

Took a look and found it: GitHub - quavedev/montiapm-mcp · GitHub
Good job @renanccastro !

[renanccastro]

Thanks @storyteller !

We created MCP initially to analyze data from one of our customers at Quave, and then decided to package it so other Meteor folks could benefit as well.
It’s been very useful for us to quickly identify low-hanging fruit and improve performance.
Good to hear it’s helping others too!