Hello HN, co-creator here!<p>With Deta we are exploring ways to make the cloud less of a monster.<p>As a dev who worked in sales and marketing, I always had ideas for small web tools to improve my own and my team's workflow — but I always faced hurdles, like setting up a server, configuring an http proxy and implementing auth.<p>With Deta, we are trying to take away these repetitive tasks and allow you to simply build your web app, not the environment it runs on.<p>We would love any feedback / questions / comments you may have!
This sounds cool but one bit of feedback in terms of prioritization<p>> DetAI (pretty soon) – No-code neural nets to auto-fix bugs before they happen.<p>I (and I suspect others as well) don't really need no-code auto-fixes for code. What I want is simple workflows for training WYSIWYG AI models. I'm not interested in writing python to express the model's computation graph. All I want are some blocks that I can glue together into a tensor graph and then deploy it for training and inference.
I think you might be underestimating the fact that your marketing copy is a good proxy for your product commitment in the long run. I am having difficulties adding you to the short list of "platforms to be considered when starting out a new project" mainly for this reason alone..<p>Best of luck though, i just wanted to give honest feedback
Hi, thanks for posting this. I have two simple lightweight use cases and I would like to know if those fit to this platform or not.<p>1. A simple Python script with two-three dependencies that needs to be run everyday once. Basically I am looking for a crontab in the cloud.<p>2. A very lightweight script that needs to be run 24/7 and would not consume more than few MBs of RAM ever.<p>None of these two needs an HTTP endpoint.
can you tell a bit more how deta compares to similar (?) services like firebase, netlify, vercel?<p>(don’t worry if there isn’t a great “usp” answer, just interested in learning more)<p>I’m personally quite excited about getting the journey from idea to something to tinker (and shareable) back down to how I remember it from a few years ago where I just live-edited files on a server. I tend to over-analyze all the various tech stack and deployment aspects too early :(<p>For hackathons I’m currently also using repl.it and glitch to get immediate results.<p>edit: kudos to getting this shipped/launching, can relate to how difficult it is to get an initial version out!
We changed the URL from <a href="https://www.deta.sh/billion-ideas" rel="nofollow">https://www.deta.sh/billion-ideas</a> to the project home page, which is more appropriate for Show HN.<p>We also changed the title from "Show HN: A Cloud for the Next Billion Ideas", which is too baity for HN. I always advise startups (especially YC-funded startups when they prepare their launches) to rigorously take out any sales and marketing language from their text and titles. HN readers are averse to it.<p>The basic rule is: Don't try to sell them, try to interest them. If you sell them, they will close the tab. If you interest them, they will sell themselves.
Why did you link to the ideas page?! There are 839 words on it and I have no idea what your product is or does.<p>After looking at the docs[1] and front-page, you're a serverless lambda/functions/zeit with all the normal limitations, but a pretty decent tech-specs for the free and paid tier.<p>What makes you different? I really like the lack of vendor lock-in, but you need some more killer features to stand out.<p>1. <a href="https://docs.deta.sh/docs/micros/about" rel="nofollow">https://docs.deta.sh/docs/micros/about</a>