Cloud Computer by Manus - A dedicated cloud machine for bots and software
by•
Manus Cloud Computer gives you a persistent machine in the cloud to run bots, Python scripts, apps, databases, and scheduled jobs 24/7. No DevOps, no server setup, no coding required. Just describe what you want to build, and keep it running around the clock.
Replies
ZeroHuman.
Excited to hunt Manus Cloud Computer today.
Manus Cloud Computer gives you a persistent machine in the cloud to run bots, Python scripts, apps, databases, and scheduled jobs 24/7. No server setup, no DevOps, no coding required.
Instead of spinning up temporary tasks, you get an always-on environment where files stay put, tools remain installed, and ongoing projects can keep running long after the chat ends.
What stands out here:
• Run bots, scripts, and software around the clock
• Keep files, tools, and projects persistent across tasks
• Host databases, self-hosted apps, and scheduled workflows
• Build and operate everything in plain English
If you’ve ever wanted to run automations that do not stop when your laptop sleeps, this is definitely worth checking out.
RiteKit Company Logo API
@byalexai This is a solid positioning around the always-on persistence angle. The 'no server setup' promise will resonate with people who've been burned by DevOps friction before. One thing I'd be curious about: how are you handling the cost transparency piece. Cloud pricing can get murky fast when you're billing for persistent machines, so being upfront about that will probably matter a lot to your early users.
minimalist phone: reduce your screentime
By the way, any information on what will happen after China blocks Meta's acquisition?
Build Check
Wow! Sounds super cool, Tao! Seeing too big competitors there but I'm sure you'll get you place. What's your main differentiation?
@hidecloud Keeping long-running workflows alive without babysitting infra is still harder than it should be. Interesting to see this simplified.
Question on the networking side. When a scheduled job is hitting public APIs 24/7, does each cloud computer get a dedicated outbound IP, or is it a shared egress pool? Asking because shared IPs eventually land on Cloudflare/WAF blocklists from someone else's traffic, and you find out by your job silently 403'ing for days.
I love the 'no DevOps required' promise. I'm curious about the networking side: does each instance get a dedicated IP to avoid WAF blocklists? Congrats on the launch.
The dedicated cloud machine angle is interesting basically offloading the entire agent runtime so your local machine isn't the bottleneck. How does it handle long-running tasks that span hours? Does it stay alive or need babysitting?