We are not running on top of Twilio. We use multiple tier-1 aggregators for redundancy and Twilio is not one of them. In-fact Twilio also uses some of them.

Numbers are sourced from DID wholesalers.

Absolutely, I get the concern about the docs looking like a placeholder. We're putting a lot of effort into crafting the best SDKs for major languages, so for now, the most comprehensive guide is at https://docs.postack.dev/api-reference/introduction.

Regarding A2P messaging, it's pretty standard: create your brand and campaigns, typically with a 72-hour turnaround. We're streamlining compliance by auto-generating legal documents, webform screenshots using templates, and leveraging ChatGPT to preemptively fix any issues before they reach upstream carriers. It's all about making the process as smooth as possible for you.

On Twilio: It took me a staggering three weeks just to get my business profile reviewed and approved, followed by another 2-3 weeks of back-and-forth communication to get my campaign off the ground. It was a real test of patience.

Not meant as a nitpick but lots of links to docs are "dead" or redirect to that placeholder. quick example: on your home page both compliance links go nowhere.

Compliance pages are still WIP. Just fixed other links. Thanks for help.

It was already there. I should have added it in Navbar too which I just did. Thanks for correction.

https://postack.dev/pricing

you should tell us what "per segment" means. Never heard of it. I use twilio mostly.

Twilio also charges per segment, they are probably not transparent. So a segment means 160 characters (It’s a bit more complicated than that).

So if you want to send an 320 characters long SMS. You are sending two segments.

Let me know if it makes sense?

that makes sense. you should put a * with a defintiion or something

I'll add a tooltip.

Have you ever had an SMS get chunked into two?

A segment is the character (really byte) limit for a single message.

I'm gonna give it a try with your video. If I may ask how many speakers are there in this video. (I have to go through all of it otherwise). From what I can see, we have a teacher who is speaking most of the times and then few laughs from students in the background.

There are a couple of people interejecting with answers to questions, or asking questions. I'm afraid I don't have a better estiamte than that. But in this case, I think lumping the students together as one speaker and the teacher as another would be fine.

I have attached a link to Google colab with the article.

https://colab.research.google.com/drive/1X5XTiob6irFq8NJM831...

Why did you guys move away from discourse?

Well there are definitely some advantages of serverless i.e.

- you don't have to create docker images and complex CI/CD pipelines. - You don't need to worry about deployments (using Heroku, AWS ECS or Kubernetes) and scaling. - you don't need to write a lot of unnecessary boilerplate code which you do in the case of micro-services. - You pay per invocation and resources used for that invocation.

But then serverless comes with all the issues which I have described in original post. I think serverless is good for quick prototyping but for production use, we should still be using micro-services. It'd be idea if we can create a new layer of abstraction which has good things of both micro-services and serverless architectures.

That's right ! Thanks for this accuracy and for sharing. Maybe you can create your own tool which takes good from both architectures ? ;)

Gusto

Thanks. Did you evaluate any other options, such as Zenefits, Paychex or others. Are you happy with Gusto?

You can use Webflow or if you want something quickly then try Product Hunt’s Ship.

Yeah just confirmed. Thanks.