We can totally appreciate that everyone has their own price points. That said, I do want to clarify that Jelly is not priced per user. The starting plan is $29/mo for your entire team. Period. In the landscape of similar tools, we think that’s quite a lovely deal.

For some folks, that’s still expensive. We get it. If so (especially if you’re a nonprofit or educational institution or...) reach out to us and let’s talk!

For small teams, it's expensive. You need a third tier for up to 3 people, or even just a duo plan.

OH

,

NO!

Thanks for the heads up! We’ll crack open the CSS...

The short story is that Good Enough has put a handful of (hopefully) delightful things into the world: https://goodenough.us/

Putting things into the world means getting emails. Being a team means juggling said emails about things amongst several people.

Enter the Shared Fastmail Account.

"Oh! A new email. Click. Oh, this isn’t really for me. Mark as unread. Or did someone else already read this, mark as unread, and think it was for me? I guess I will go talk to..." And, you know, two dozen variations on that theme. It sucked as a way to work together.

  what benefits does this provide over something like Slack or Discord for small teams?

We use Slack at Good Enough. It’s nifty. We even have a Jelly + Slack integration (and we use that too)! That said, the problem I described isn’t really solved by Slack. (Maybe Discord if you’re in a space that can funnel interactions there, but obviously there’s a lot of businesses who aren’t, and there’s a lot of drawbacks to using Discord as your only communication medium.)

Email is still widely used and wildly useful. We think being able to collaborate on emails as a team, with clear expectations about who is handling what and visibility on all the back and forth, is really helpful. We’ve been using it to scratch our own itch from day one, and we suspect it will be of interest to others as well!

Let me know if any of that didn’t make sense or you have any other questions.

Thank you for the detailed reply.

I now understand how this is specific to solving the problems of a shared email inbox. This isn't a problem I've had to deal with before, but indeed it appears to be a sufficiently painful problem to solve for.

I wish you the best of luck, and continue the good fight to simplify.

Thanks for the kind words (and for passing Jelly along to others!).

  Maybe my only suggestion would be different kinds of archiving

Definitely something for us to consider. Thanks for the feedback!

  Also I see the Trix WYSIWYG editor, rails? :)

You nailed it! The Good Enough crew have all been long, long time Ruby/Rails fans. We’ve even landed a few commits into Rails along the way. :)

Thanks for the kind words! We’re definitely trying to spread more decency and reason in the world. :)

  I'm going to send this around to some people.

Even bigger thanks! It’s hard to ship stuff, and it’s even harder to spread the word.

Yes! Jelly was born out of a shared Fastmail account. You can forward your email to your dedicated Jelly address and be jamming (sorry not sorry) in no time. Don’t hesitate to drop us a line if you have any questions or feedback!

ah yay! I'm using Front right now for this but I'll look into using mail forwarding!

would mail still be sent from our Fastmail servers?

Jelly itself does the sending, although we are exploring sending from your existing mail provider.

  Love the product and you've nailed the simple design!

Thanks for the kind words!

  I'm concerned about email deliverability

As I’m sure you can imagine, we’re very concerned about email deliverability. We use Postmark to send email and deliverability hasn’t been an issue thus far, but your verification email ending up in spam is not cool. I would ask some followup questions here, but troubleshooting this on HN isn’t ideal for either of us. Any chance you could drop us a line at https://letterbird.co/jelly if you’re willing to dig a bit deeper with us? Sorry for the less-than-stellar experience thus far!

I also liked the landing page.

Constructive criticism, might just be me: I would lose the phrase "jam on email"... something about it (too folksy?) rubbed me the wrong way.

Perhaps something simpler like "Say hello to Jelly, team email done right."

For a counterpoint - I like it! "Jam" reminds me of jam sessions and FigJam, both pleasant experiences.

Good questions! Most of our products are built with a pretty vanilla Rails stack (what we’re most familiar/comfortable with) backed by Postgres. Beyond that, it’s just the classic engineering struggle of trying to keep things simple and maintainable while making tradeoffs to ship stuff that’s Good Enough™. :) Happy to speak to any more specifics if you have further questions!

Cool! What about deploying?

Jelly is currently using Render, and we have automated deploys set up from Github, so just merging the PR kicks off the magic sauce.

taking off my Jelly hat

I’ve also used Kamal + Hetzner for a few other simple things recently, and it’s been surprisingly delightful (speaking as someone who has never enjoyed mucking about with deployment frameworks).

Por que no los dos?

( ͡° ͜ʖ ͡°)

I see what you did there.

Jelly’s here for you when it stops being, well, good enough!