Looks great, will try it in a new project I have.
1 Like
Amazing progress you made, congrats. I have an account but haven’t been able to make sure it runs and populates with data properly. It’s on my list but I’m drowning in work and I wish I had your rate of productivity.
Keep up the great work!
1 Like
After migrating to Meteor 3, this was one of the applications I was most excited to use. I connected our application, which runs on 3.4, to SkySignal. Apart from a few cosmetic issues, I think everything went well. For example, I searched for the “meteor add” command inside the modal where the sample settings.json is located. These were minor issues.
The main problem is that the UI is incredibly slow. It doesn’t even open right now. I’m still looking forward to trying Astra, but the current product isn’t available at the moment.
I know the project is new, and it looks great and intriguing, from the concept to the design language. I don’t know how I can provide support in this regard. I’ve attached a screenshot.
Sorry to hear you weren’t able to get the site to load. About what time were you experiencing this issue?
Are you still unable to access the app?
3 hours ago. It was fine 1 hour ago, and it’s working now without an issue. I love the Request Flow chart.
1 Like
Got it. I’ll investigate the infra state from 3 hours ago.
Glad to hear everything is working for you now.
Edit: Overall, what are your first impressions of SkySignal? In your previous post you mentioned the missing ‘meteor add’ command — I’ll get that fixed.
Also, try out the mobile version of the site if you have time. A lot of time was spent on trying to polish the mobile UX — DevOps and troubleshooting needs to be accessible wherever you are and not feel like a burden to navigate.
Mobile version is a must in monitoring apps. Glad to hear it.
I will use it on both Mobile and Mac. We are just launching the app, so we will check it regularly and I will inform you from here.
1 Like
Thank you for everyone trying out SkySignal.
Dropping this here to combat the sentiment that “Meteor doesn’t scale”.
4 Likes
Okay, that’s exciting!
1 Like
Currently paying $100 per month for MontiAPM. Currently throws SWC errors when building in Meteor 3.4.1 with rspack. No response from developer on customer support channel or any forum.
SkySignal 
Give it a try! Let me know what your feedback is! 
1 Like
I’m really sorry about that. I just published an update that fixes the swc errors.
3 Likes
New: Mergebox Memory Accounting — finally see which publications are eating your server RAM
One for the pub/sub-heavy crowd. You know the mergebox: Meteor’s per-connection, server-side cache of every document each client is subscribed to. It’s also the single largest and least-visible consumer of server RAM — the usual reason a busy app quietly creeps toward an OOM. Every APM can tell you the heap is climbing; none of them can tell you why, because the mergebox is a Meteor-only thing.
SkySignal now measures it. 
The new Mergebox tab (under Real-time) attributes mergebox RAM residency — the actual cached copy sitting in memory, not bytes-on-the-wire — down to the individual publication and collection holding it. So instead of “heap’s at 1.4 GB 
”, you get:
-
RAM by publication & collection — who’s actually holding the memory, ranked. -
Publication strategy per collection — SERVER_MERGE/NO_MERGE/NO_MERGE_NO_HISTORY/NO_MERGE_MULTI, with a built-in explainer of the server-vs-client tradeoff (for when you can’t remember which one skipsremovedon stop… it’sNO_MERGE_NO_HISTORY). -
Reclaim candidates — “messages.forChannelholds 220 MB across 1,400 connections — switch it toNO_MERGE.” One click hands it to Astra (our AI) for a recommendation. -
Residency over time — an actual answer to “why has memory been climbing since Tuesday?”
It’s collected agent-side via a low-frequency, read-only snapshot of the live session caches — sampling-bounded so it’s safe on large fleets — and it’s opt-in:
// settings.json
{ "skysignal": { "collectMergebox": true } }
Needs @skysignal/agent v1.1.0+.
6 Likes
@mvogt22 Given the rapid pace of newly shipped features, it sounds like SkySignal is very much riding the AI development wave. This is fine and all.
Where is SkySignal with security? Do you have any comments on what data protections you have? Where are your servers located? Is the encryption HTTPS SSL then from our servers to yours? Something else - more or less?
We’re curious to give it a shot, but the agent-coded vibe is giving us some pause. Not that we won’t love a lot features and fast development.
Don’t see much on the landing pages. Thanks!
2 Likes
You are 100% correct – I leverage agentic workflows to build SkySignal.
I believe AI is revolutionizing productivity for builders, but also lowers the barrier to entry for newcomers or what are now known as vibe coders.
At the end of the day, AI agents cannot be held responsible, they are tools for humans. The humans are the one’s held responsible.
I digress, to answer your original question. Yes, SkySignal utilizes industry standard security, extensive CI testing (Trivy, dependency monitoring, etc.). Data is encrypted in-transit and at-rest.and hosted with Quave’s platform.
1 Like
What geographic location for the servers and database if you don’t mind?
Hosted in Ashburn, VA, USA
Have you done expansive Pentesting? When I did it for my app it brought up quite some surprises that I had to urgently fix.
1 Like
What tools did you use for pentesting?
I’ve asked Claude Code to do the Pentesting and it came up with 10 different phases (well 9, the 10th was the final, combined report), including a long list of questions for Quave which Filipe luckily answered very quickly.
As it goes over your code base (of several projects that form my project) it takes a different approach vs what a (whatever hat) hacker would do from the outside.
2 Likes