Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Launch HN: Epsilon3 (YC S21) – Software for spacecraft and complex operations

news.ycombinator.com

Post reply on HN
Print view View original

41–50 of 63 posts

Re: Launch HN: Epsilon3 (YC S21) – Software for spacecraft and complex operations

#41

Post by alchemistmax »

techdragon wrote: post #40
alchemistmax wrote: post #24

Earlier quoted context omitted.

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'…

I’m building up a space related non-profit (space telescopes) and I’m not in the USA. So ITAR is a poison, it is great you have an ITAR Free option, do you have any plans to host in other AWS regions long term? And how much more is on-premises likely to cost me?

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?

Re: Launch HN: Epsilon3 (YC S21) – Software for spacecraft and complex operations

#43

Post by lavezza »

llcrabtree wrote: post #34
lavezza wrote: post #21

Laura, congratulations. Does it support acronyms? :) Anyone interested should sign up for the changelog emails. It's only 1-2 emails a month and shows how much progress Laura and her team are making.

Lol, thanks Pat. I keep telling the team that we won't allow acronyms. That feature is 100% on the list. Currently they are allowed, however future revisions might not allow acronyms, or might force you to define them. Certainly keep your eyes peeled for this new *feature*.

I was just kidding of course, but the idea of defined acronyms is interesting. Hover over an acronym and see the expanded text.

Re: Launch HN: Epsilon3 (YC S21) – Software for spacecraft and complex operations

#44

Post by llcrabtree »

aml183 wrote: post #39
k1rcher wrote: post #32

Earlier quoted context omitted.

Cool service. FYI: after signing up with the MailChimp form, clicking the “Continue to website” link on the signup confirmation page results in a 404.

Thanks, we just built a new site and hiring some journalists. The MailChimp was just MVP to see if people cared about space news (which they clearly do). Expect a much more professional site in the coming weeks.

Yes! Super excited about this too. We love seeing information being shared about this industry more freely than before! And an increased interest doesn't hurt either. =)

Re: Launch HN: Epsilon3 (YC S21) – Software for spacecraft and complex operations

#46

Post by llcrabtree »

k1rcher wrote: post #30
llcrabtree wrote: post #17

Earlier quoted context omitted.

Joseph, for #1, I've worked on in-house tools and: 1. They never get enough developers. 2. They usually get deprioritized in lieu of other projects. 3. Many small space companies don't have resources to build awesome in-house tools. It can be really time consuming and take the team's focus off of the primary goal as well, so we try to get teams to focus on the things that they are uniquely qualified to do, rather tha…

> 1. They never get enough developers. 2. They usually get deprioritized in lieu of other projects. As a dev currently building out several fairly-complex in-house tools for a small startup, I can relate to this first-hand. It’s enormously frustrating as a perfectionist with a slightly neurotic obsession with (in a balanced and healthy way, trust me ;D) and appreciation for best practices, I have had to (against bett…

This is 100% my experience too. Something has to give when you're developing a tool for in-house use only. The same practices you'd use for developing a tool for a larger audience can't apply because you don't have endless resources, personnel or time when developing in-house. Thanks for this information. It's super helpful!

Re: Launch HN: Epsilon3 (YC S21) – Software for spacecraft and complex operations

#47

Post by llcrabtree »

lavezza wrote: post #43
llcrabtree wrote: post #34

Earlier quoted context omitted.

Lol, thanks Pat. I keep telling the team that we won't allow acronyms. That feature is 100% on the list. Currently they are allowed, however future revisions might not allow acronyms, or might force you to define them. Certainly keep your eyes peeled for this new *feature*.

I was just kidding of course, but the idea of defined acronyms is interesting. Hover over an acronym and see the expanded text.

100% on the roadmap!!!

Re: Launch HN: Epsilon3 (YC S21) – Software for spacecraft and complex operations

#48

Post by llcrabtree »

allyew wrote: post #22

Really excited to be part of this team! Laura was talking yesterday about tearing up at after the Blue Origin launch, not just because it's amazing to send people to space, but because it requires the work and communication of thousands of people to take them up and bring them home safe. We're excited to build tools to enable all of the hard work that leads up to a successful launch!

yes to this! It takes a huge team to make something like that successful, and we want to continue to support those teams!

Re: Launch HN: Epsilon3 (YC S21) – Software for spacecraft and complex operations

#49

Post by llcrabtree »

spops_anonymous wrote: post #45

Oh, it’s llcrabtree! We didn’t cross paths but I’ve seen your name all over Confluence. :) (I was on the training team after you left.) This is gonna be rad. Can’t wait to see where it goes.

Oh it is LLCrabtree! I'd love to connect. Send me an email laura@epsilon3.io =)

Re: Launch HN: Epsilon3 (YC S21) – Software for spacecraft and complex operations

#50

Post by alchemistmax »

heaths1 wrote: post #23

Looks very interesting. I surfed around your site and watched the video. So how about nonconformance processing? Do you have workflows for that, or is that where something like JIRA comes in? Also, have you utilized anything like the S1000D aerospace data schema with this tool, or are you rolling your own?

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.

Post reply on HN