AI can draft a reply, build a small app, or run a routine task. But being able to automate something does not always mean you want to hand it over.

Sometimes doing it yourself is how you notice a problem or understand what someone actually needs.

A user uploads a file, starts an export, and closes the tab. The work may still be running, but when they come back, they need to know what happened.

I am building Inquir Compute for apps, databases and background jobs. I am interested in the part users see, beyond whether the job itself succeeds.

A first version can do one job well and still feel unfinished.

There is always something else you could add:

• Team accounts

• Billing

• Integrations

• A better onboarding flow

Your app is online, the main flow works, and you want to step away for the weekend.

What would you check before closing the laptop?

I recently built a small PDF editor with AI for myself. That got me wondering about another use for these small apps.

Has anyone here built a free tool specifically to help people discover their main product?

I m getting Inquir Compute ready to launch. It s a platform for running apps, databases and background jobs, and it s where I host the editor. Alongside sharing what I m building here, I m looking at other ways to reach developers.

A small tool for the same audience sounds worth trying. But I don t know how often that turns into customers, rather than a second app you now have to maintain.

I recently built a small PDF editor for myself. I wanted something free that I could open in the browser whenever I needed it.

With AI, I ll just build my own seems like a reasonable option for more of these small problems. Especially when you only need a few features and the tool only has to fit the way you work.

I suspect a lot of useful AI-built software will end up as something someone keeps in their bookmarks and uses every week, without ever trying to turn it into a business.

I m hosting the editor on Inquir Compute, the platform I m building for apps, databases and background jobs. We re getting close to launch, and I d like to hear about the things people are building for themselves.

Show me the version you have right now.

I d like to see what people here are working on before the demo is polished. A screenshot or a link is enough, along with what it does and the next thing you re trying to get working.

I m preparing to launch Inquir Compute, a platform for running apps, databases and background jobs. In my last post, I asked about tools people had built for themselves with AI. This time, I m interested in the projects that are still in progress.

What works already, and what s keeping you from sharing it with your first users?

I m building Inquir Compute, a platform for running apps, databases and background jobs in one workspace.

AI tools are helping more people write working applications. I m interested in what happens next, when you need to put that app online and keep it running.

If you ve deployed something you built with AI, where did you get stuck? Build errors, database connections, environment variables, unexpected costs or something else?

A couple of my recent posts led to good conversations. Now I m trying to figure out what gets someone from reading about a product to actually trying it.

For those who ve launched something: where did your first users come from? Were they following what you were building, or did you find them somewhere completely different?

I m getting Inquir Compute ready to launch. It s a platform for running apps, databases and background jobs. I ve been sharing what I m working on here, but I m still figuring out how to reach the people who might use it.

Share your product and one specific thing you did that brought in users.

I like Lambda for a lot of things, but there s a very specific point where it stops feeling elegant.

Usually it starts with something like:

• a job that runs too long

• a workflow that should keep going in the background

• a task that needs better isolation or custom runtime behavior

• a system that starts needing cron, retries, webhooks, logs, and routing in one place

And then the answer often becomes: move to Fargate, ECS, Step Functions, EC2, or stitch multiple services together.