raphaelcosta

It’s curious what they said in the email they sent me about the OSS version.

------

A few important changes to note:

We will no longer provide public Docker images, so your team will need to build the image yourselves.

Please do not use Cal.diy — it’s not intended for enterprise use.

> *Apple TV* is available on the *Apple TV* app in over 100 countries and regions, on over 1 billion screens, including iPhone, iPad, *Apple TV*...

Which semantic layer they are using?

It's just another template engine, we can do the same (components like templates) in any language for years.

Ruby example that Github is using: https://viewcomponent.org/ https://viewcomponent.org/viewcomponents-at-github.html

Doesn’t make any sense for me why we are now using React in the backend, to render HTML… Let’s go back to 10 years ago.

It works with Supabase self-hosted?

How does it work with custom objects that customers have inside Salesforce? Each end-user can select which custom objects they want like to sync?

How many conspiracy theories people will create/associate using that story?

We identified the issue and fixed! Thanks!

We identified the issue and fixed! Thanks again!

Thanks! I basically checked how other embeddable companies are doing, but you are right, I think it could be simpler now, thanks!

I was not able to reproduce, but I changed some resize code, could you please check if it's still happening? Thanks!

Thanks for the feedback! I will fix those typos.

where? :)

We used third-party services to generate that, and that's why we redirect. We are looking to migrate that to our end in the future. Thanks for the question!

The stack is Rails, React and GraphQL. We are using Heroku for hosting right now, but we are looking to move to AWS.

Thanks, trying to reproduce here.

Thanks, trying to reproduce here.

Sure, I was imagining not a percentage of the revenue, but plans based on how much revenue they are making with their SaaS tool. Ex.: If you make more than 10k MRR, you need to be on the Business plan.

Thanks, @runako! Thanks for your feedback regarding pricing, get tied to revenue could be a great pricing strategy. We got featured on ProductHunt today, would be very nice to have your feedback there also.

Good point, I was trying to make the snippet simpler, since this is not required for Stripe setups, but I agree that this should be more clear. Thanks for the feedback!

We have support for Recurly but not for Stripe today, but we can easily add support for that. Do you have any specific need?

We are using your Stripe token in our backend to get the subscription information, and we also rely on identity verification to make sure that none of your customers can impersonate another one by guessing another Stripe Customer ID (https://docs.pubilling.io/quick-install/identify-verificatio...). Make sense?

We have plans to add this feature in the future, but it's not a priority today since Recurly and Stripe already send those invoices to the customers. Do you have any particular need for that? Thanks!

Thanks! Which browser are you using?

Thanks for the help! Fixed :)

Thanks!

Awesome! Congrats Heroku team!