alchemistmax

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.

Comment · 5 years ago

Thanks!

Comment · 5 years ago

Yep, we are planning on hosting in other AWS regions as well. For pricing, let's discuss offline because it'll depend on a few things. Can you fill out the Contact form on our website (https://epsilon3.io/contact), and we can take it from there?

Comment · 5 years ago

So grateful for your kind words and honored to be supporting your team!

Comment · 5 years ago

Thank you for the kind words and great questions.

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.

Comment · 5 years ago

Thank you!

Comment · 5 years ago

Thanks! That's nice to hear. You can see our job openings, which are remote-friendly, at https://angel.co/epsilon3/.

Comment · 5 years ago

Thanks! No, the US Government can't access your data. Only you can. GovCloud is just a special portion of AWS that has extra security controls so that US companies are confident that all their data is housed in US servers and properly treated according to ITAR regulations. It's totally fine for companies outside the US to use and doesn't give the government any access.

We also support on-premises deployments if that's preferable to companies outside the US.

Comment · 5 years ago

Nice! Thanks for great ideas and questions.

1. Building in house is expensive, slow, and painful, and most teams have better things to spend their time on. We’re helping several teams move off their in-house solution because they aren’t satisfied with it.

2. We are building out automation and scripting capabilities. We support integration with Python scripts and other local commanding destinations via our API.

3. Love the idea! We already support real-time comments that are embedded in procedures. We want to build out even more things along those lines to streamline communications.

Comment · 5 years ago

There's a ton of time wasted in miscommunications and lost paper records or illegible handwriting on test logs. And there have been many disasters and lives lost in the past, so anything that can be done to avoid that is worth seriously considering. Plus we make it a nicer experience and way faster.