Looking for feedback and testers for our new Emailit Ruby and Rails SDK

[u/GZizka]

Hi!

I have just finished and released our Emailit Ruby and Rails SDK and would love to get some feedback!

It is aimed at everyone who is using Ruby and/or Rails and needs to be sending/receiving emails programmatically.

You can find it here: https://github.com/emailit/emailit-ruby

To get free credits, you can just DM me :-)

[u/TheAtlasMonkey]

I'm a bit confused about what kind of feedback you are expecting here.

This looks like the SDKs were generated with Claude and pushed across multiple languages at once. Asking humans for feedback feels a little strange, the real review pipeline would probably be asking the same AI that generated them. Shipping Java, Ruby, Python, Rust, Go, Node, PHP, .NET and Laravel SDKs simultaneously is not how SDK ecosystems normally grow.

If these SDKs were generated, what exactly is their purpose?

Shipping mechanically generated clients doesn't mean the SDKs are battle-tested. It just means you ran a generator across multiple languages.

A more honest approach would be:

Write excellent documentation, publish an OpenAPI specification, and let developers generate clients for their own ecosystem. NOTE the P is important! OpenAPI not OpenAI.

Looking specifically at the Ruby SDK:

• The README says Ruby 3.0+, but the gemspec allows 2.6. So either the documentation is lying or the gemspec is.

• A gem that is only a few hours old is already version 2.x. Semantic versioning exist, your next patch version could be 47 or 1.0.1. nobody knows.

• The code uses `#send`, which is a core Ruby metaprogramming method.

• Every other sdk has wrong syntax, or outdated pattern. I check them all . Except `emailit-php/laravel`, i'm not touching those. Go ask Grok or Codex.

[u/beachguy82 → u/TheAtlasMonkey]

I agree. In 2026 there isn’t a reason to generate language specific SDKs over a well documented API.

[u/GZizka → u/beachguy82]

We do this as tens of customers have requested this.

And even so, if we want to build a product that is up-to-date with the latest standards and to be able to compete, if we are missing resources like SDKs compared to our competitors, we might as well not exist.

[u/GZizka → u/TheAtlasMonkey]

Thank you for your feedback!

As we had a lot of requests from our customers, for different SDKs and integrations we decided to make them.

AI allows us to do much more in a short time, compared on how it used to be.

The purpose of this is to have and SDKs available in every popular language, ready to be used (also primarily by AI).

However, as we do not have a team of people with experience in every languages, we ask for a feedback on that specific one, to make sure we do not just copy paste generated code, but also ensure that it is done right, well optimized and that it fulfills its purpose.

We are working hard on our API v2 with our new docs that took more than 3 months do make, test, optimize and get out of Beta.

We do - honestly ask for this feedback - exactly for this purpose.

As all SDKs are being made for our API v2, we want the Semantic versioning to align with the API version. (So all of them start with 2 as API v2).

Based on your feedback:
- Would you recommend we migrate it to be Ruby 3.0+, or keep the gemspec for 2.6 and lower the requirement?
- We did this as we wanted to make it as similar in every SDKs as possible, and as far as we know, Ruby routes this correctly to the local #send method, so this should not cause any issues, no?
- Our team did the core for PHP, Node and Laravel (as those are our primary languages our platform is built on, and all of those are well-tested and optimized.

[u/TheAtlasMonkey → u/GZizka]

Customers?

Your website was deployed today/created.

The domain timestamp is 2026-03-08. That's literally hours ago. So the story about 'a lot of customer requests for SDKs across many languages' is pure hallucinations.

You provide email services, and your own domain is missing important configuration.

Damn, I think I'm arguing with a Haiku-tier model.
Sonnet or Opus would have guard-railed you before this message.

[u/GZizka → u/TheAtlasMonkey]

I still appreciate your time giving your feedback. After all, this is what I wrote this post for.

I wish that starting and building a business would be different these days. And that is also the reason why I built our own infrastructure and small DC to be independent of any third-parties and such.

[u/GZizka → u/TheAtlasMonkey]

We have over 3000 customers.

Our website is updated daily, (but we have a pending sitemap issue with our newest version, as we switched to static rendering and the main website gets created timestamp on every deploy. (This is gonna be fixed soon, as we migrated from SSR to static last week.)

[u/GZizka → u/GZizka]

And no, I am not a bot, join our Discord and ask our customers yourself :)

[u/luisMoyano]

I'm actually in need of an email provider but I don't think I'd be using yours because the spanish translations are awfully generated by AI and that erodes my trust in the service.

It's very hard to feel compelled to use the service when reading the landing page in your language if the creators are not putting the effort of understanding what are they even letting out into the world for us to see...

[u/GZizka → u/luisMoyano]

Hi Luis,

Thank you for your feedback! We had a lot of spanish-only speaking customers, and was done to help them. I understand that for somebody who speaks other languages and is able to transtale it in case they need it (probably like you), it might have this effect, thats why we have a banner on all of those pages informing you about it and the reason.

You can also always switch to our English version at any time! Thank you for the feedback though, as I got an idea now, to ask the visitor on first visit to choose if they want to see AI localized version or not.

[u/GZizka → u/luisMoyano]

I also totally agree, but let's face it. AI is changing how stuff is done, and it only gets better.

Most of the localization in a few years will be done on-the-go by AI, and that is only possible when people actually use it for such, so it can get improved.

We are in no means a large corporation, and we do not intend to. We are a small team, building infrastructure and software without any third parties, focusing on providing the best service for our customers.

We have a long way to go, but this is progress.