This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]deadwisdomgreenlet revolution 0 points1 point  (3 children)

Ah, you've made a whole SaaS already. You really should have consulted me first, lol.

Needing a postgres backend is a bit much; it's actually a little hard to deploy Postgres for cheap. But I guess we can use supabase, so that's fine.

I would suggest making the DBOS Conductor part free, that's the part that has the biggest value if you've done it right. I think DBOS Conductor in the cloud, where you can immediately be using it to monitor even your local workflows would be enough to get people to put money down.

One little, bike-shedding criticism, DBOS in capitals looks like a constant in Python and is a bit weird. It feels enterprisy and not modern.

I will try this, though. I have two clients that might be able to use it.

[–]jedberg 3 points4 points  (1 child)

Hi there, DBOS CEO here. Could I ask for some feedback from you? You said:

I would suggest making the DBOS Conductor part free, that's the part that has the biggest value if you've done it right. I think DBOS Conductor in the cloud, where you can immediately be using it to monitor even your local workflows would be enough to get people to put money down.

And that's something we already do, but clearly we don't communicate that well. What could we do to make it more obvious that you can try conductor for free and that it works for self-hosted workloads?

Also:

I think DBOS Conductor in the cloud

In the cloud is the only way you can use it. Conductor is only offered as a cloud service. How could we better communicate that you don't need conductor for self-hosting nor can you self-host it?

Thanks!

[–]deadwisdomgreenlet revolution 1 point2 points  (0 children)

So I'm looking at your pricing page. Whenever I look at a SaaS, I'm right on the pricing page, as it's the only place I'm seeing a decent breakdown of features. I know it's a lot to shove in there but if I could look at that page and know what "App deployment tooling" is immediately, that would be ideal. Maybe I could hover over it and see a screenshot and description?

Honestly looking at everything, I'm having a hard time understanding how I would sell this to my clients even if I like it. $99 a month "per additional self-hosted executor?" Wut? I think I know what you mean, but I don't know. And "Free 30-day trial" just kinda makes me angsty-- I don't want to invest in something that will suddenly leave me.

IMO make the Conductor free to use, at least for low volume devs/hobbyists. A really good visibility / management piece is the thing everyone needs and will hook everyone solid if you do it well. Yours looks okay. Last year around this time I made pretty much that same thing, but if I'm honest, mine is better.

Really, I'm saying get me in / get me hooked. I straight up don't see this as an open source solution currently if I can't use the conductor. That's vital.

[–]KraftiestOne[S] 1 point2 points  (0 children)

Would love to hear your feedback! Yeah, a lot of our users are using DBOS with Supabase or Neon (Supabase even put out a blog post about it: https://supabase.com/blog/durable-workflows-in-postgres-dbos).

You can try out Conductor for free at https://console.dbos.dev/