2
2 Comments

Released beta, would love feedback (low-code for non-engineers)

Hello! I'm a big data engineer turned entrepreneur. We've recently released a beta product, and I'd really appreciate feedback (negative included). We built this to scratch an itch we saw at our last company (LiveRamp), and wanted to build something we can share.

Frontloaded link: our website is here, and "Try CloudWright" will drop you into a sandbox.

The story: we think there are a growing number of non-devs at companies who can script, who have business knowledge, and who could build valuable internal tooling. Right now they can't, because there's no good platform where they can script internally-connected and reliable tooling.

I know there are a lot of companies in the low-code/no-code space, but we didn't find anything that checked all of the boxes we had personally needed at LiveRamp:

  • VPC network access, so deployed tools have internal databases and APIs access
  • Data can stay on premise, in your own cloud environment
  • Lightweight SaaS integrations
    & Sharing & permissioning for a company environment
  • Deploy cloud-native infrastructure, not hidden / black-box SaaS apps

So we built a tool that makes it easy for non-dev scripters (anyone who spends a couple hours a week hacking in Python) to really build production-quality internal applications. Or, we hope.

To be honest, our challenge is in narrowing down to the use-cases which are most compelling. Some of the biggest pain points we've seen users build against so far are:

  • Lightweight stats reporting (eg, push SQL queries to Datadog)
  • File operation automation
  • Tools which wrap APIs and are handed off to business users

But I'd really like to get feedback from a wider audience. Thanks in advance, hoping to learn from the experienced hackers here.

on April 9, 2020
  1. 1

    This seems cool, and looks like it took a lot of work.

    I am an engineer and had some of the same issues when I was first started getting users to mydigitaloffice.io.

    1. Most people really have no clue. You need some onboarding even if it is very simple.
      There are people in the world who do not know ctr+v or any other keyboard shortcuts, if there is not extremely high intent to learn something new, they simply will not even try; they are a vast majority. Keep in mind the low computer literacy people!

    2. After you get paying users and probably before you should keep updating design. You never want: 'This seems like a side project not a SaaS' or 'Where is the Github repository because this seems open source'.

    3. The docs are really good!

    1. 1

      Thanks for the feedback -- really appreciate it. We'll rethink our onboarding process

      Definitely acknowledge our design could use work. We're not front-end devs, so we were hoping to get to "good enough" for a beta. We'll be iterating...

      Thanks re: docs, that's great to hear.

      Edit: meant to add -- really good timing with respect to your own startup. Not that a crisis is ever a good thing, but you really situated yourself well.