Awesome article, Ian, and thank you for the shout out to Epsilon3! We're honored and excited to be supporting all these amazing space companies in YC and beyond and helping to enable the future of exploration.
That's an interesting idea. We plan to eventually support some level of decentralization and syncing while starting with the centralized approach first.
Sure, would love to chat. That sounds like a great opportunity for collaboration. Can you fill out the form at https://epsilon3.io/contact and we'll follow up with you?
We are planning to have some dedicated functionality to help with non-conformance, anomalies, and other related things. We also plan to integrate with JIRA for separate reasons too.
We have not implemented a standard data scheme yet, but that's a great idea. We've been letting our customers set up their own schema and structure based on their needs, but I can definitely see the value of being able to adopt an industry-standard schema, so that's a great idea.
I'd love to learn more about your use case and understand better where you're coming from on those points.
We have been very thoughtful to build as flexible a framework as possible to support all those various use cases you said (not only in our user interface but also our API). We want to give end-users across the continuum of use cases the tools they need to be able to make Epsilon3 as useful for them as possible.
We have a ton of ideas on applying ML on our side for exactly those use cases you described (metrics, analysis, reporting) but also for anomaly detection, error handling/risk reduction, and continuous improvement.
We have our job openings posted at https://angel.co/epsilon3/. We're always on the lookout for strong full-stack software engineers.
