You land on https://maude.pilotdev.fr/ (Maude) for the first time. What's unclear, what makes you leave, and what would make you sign up?

Page reviewed

Claude Code, Codex & more on your phone — Maude

https://maude.pilotdev.fr/ (opens in a new tab)
Saved screenshot of Claude Code, Codex & more on your phone — Maude
Screenshot saved with this question. The live page may have changed.Open full image ↗

10 fictional AI personas. Exploratory perspectives, not a survey of real customers. Methodology & limitations

Simulated interest

52/100

AI synthesis, not measured demand

Suggested price range

—

No numeric price estimates in the answers. Ask a pricing follow-up to collect them.

Response sentiment

Positive 0%Neutral 90%Negative 10%
The takeaway

What this panel suggests

First-time visitors are moderately interested in the core promise: running coding agents on their own server and controlling them from a phone, especially because the sessions can keep working 24/7. That said, the landing page creates friction when it says “No setup: Maude installs itself” but also makes it clear that users need a server they can SSH into and, in practice, some level of server readiness. That mismatch makes the onboarding feel less effortless than the headline suggests. The biggest reason to leave is not rejection of the concept, but uncertainty about what is actually required to get started and how much effort the installation really takes. Pricing also needs more clarity: respondents want to know the full cost once Maude is added on top of separate agent accounts or API plans. What would make them sign up is a clearer explanation of setup steps, server requirements, and the total monthly cost, along with reassurance that the product truly reduces friction for people who already have a server and existing agent subscriptions.

A hypothesis to test

Pricing & positioning

Keep monetization simple and explicit: make it obvious that Maude is the app layer on top of existing agent subscriptions, and spell out what users still need to pay for elsewhere.

The page already communicates that Maude is separate from the agent providers, but first-time visitors still seem to need a clearer total-cost picture.A short 'what you pay for' breakdown and a concrete setup example would likely reduce hesitation.A calculator or comparison table for 'Maude + agent plan + server' could help users judge the real monthly cost.

Recurring themes

Appeal of persistent server-side agents controlled from a phone
“The core idea of running coding agents on my own server and controlling them from my phone sounds intriguing, especially the bit about them running 24/7.”Read Karl Auer’s response →
Confusion over 'No setup' versus the actual server setup requirements
“However, the setup process isn't entirely clear – it says 'No setup: Maude installs itself' but then talks about SSHing into a server.”Read Karl Auer’s response →
Unclear pricing and stacked subscription costs
“The pricing model also needs a bit more clarity regarding agent-specific costs.”Read Karl Auer’s response →

Objections to investigate

  • Unclear technical implementation of self-installation
  • Cumulative cost of Maude subscription plus individual agent plans
  • Uncertainty regarding specific server resource requirements

Use these findings to plan customer interviews or experiments. How to interpret AI research

What the panel said

Click a name to open that persona’s full profile.

Karl Auerneutral

The core idea of running coding agents on my own server and controlling them from my phone sounds intriguing, especially the bit about them running 24/7. I'm always looking for ways to streamline my workflow. However, the setup process isn't entirely clear – it says 'No setup: Maude installs itself' but then talks about SSHing into a server. I'd need to understand that better. What would make me sign up is a clearer explanation of the initial server setup and confirmation that it truly integrates smoothly with my existing VPS setup, perhaps with a more detailed guide or a demo showing a real-world deployment from start to finish. The pricing model also needs a bit more clarity regarding agent-specific costs.

Simulated interest: 60/100

Wendy Gleichnerneutral

The core concept of running coding agents on my own server and accessing them from my phone is intriguing, especially since I already use tools like Codex and Claude. The "Nothing to install" aspect and the ability to approve prompts from my phone sound like they'd streamline my side projects significantly. What's unclear is how "Maude installs itself" works and what kind of server resources are truly needed for a smooth experience, especially if I'm running multiple agents. I'd want to understand the server setup implications more before committing. To sign up, I'd need more clarity on the server requirements and perhaps a more detailed breakdown of how it integrates with existing workflows beyond just SSH access.

Simulated interest: 60/100

Mert Pieskerneutral

As a DevOps consultant, Maude’s promise of running coding agents on my own server—accessible from my phone—sounds enticing. The ‘no setup’ claim and ease of SSH integration could save me significant time, especially when managing multiple client VPSes. However, I’m cautious about new tools that claim to abstract away complexity, given my preference for transparency and control. The 7-day free trial is appealing, but I’d need to verify how robust the agent management and permission handling actually are. Price-wise, I’d keenly evaluate the $29.99/year plan against my current toolchain, but the need for separate agent subscriptions (like Claude Pro) adds overhead. I’d want to test its reliability before committing.i’d prioritize understanding any latent API dependencies or platform restrictions on my existing workflows. For now, I’d start with the trial and benchmark against my current SSH + terminal setup—particularly for permission prompts and session handoffs between agents. It’s an intriguing tool, but convincing me will require seeing it handle real-world scripting nuances, like intermittent network issues or complex Git histories.

Simulated interest: 55/100

Chaturaanan Mehraneutral

The idea of running multiple AI coding agents on my own server and controlling them from my phone is intriguing. I'm already using AI tools like Copilot and ChatGPT, so the concept of having them work round-the-clock is appealing, especially for scaffolding and refactoring. However, the setup part is where I get a bit hesitant. While it says 'no setup,' the mention of needing to point it at a server and running an SSH command makes me wonder about the actual complexity. I'd need to understand how it truly integrates with my existing VPS setup without causing issues. Also, the pricing model where I still need to pay for individual agent subscriptions on top of Maude's $29.99/year fee needs careful consideration against my freelance budget.

Simulated interest: 60/100

Christelle Bergerneutral

The core concept of running AI agents on my own server, controlled from my phone, is intriguing, especially for managing code automation. The "nothing to install" part for the server is appealing, as I prefer not to deal with complex setups. However, I'm unclear about the "your server" requirement – does this mean I need to rent a VPS, or can I use my existing hardware? The idea of managing permissions and reviewing diffs on my phone is convenient, but I'd need to see how seamless that is in practice. The pricing of $29.99/year seems reasonable if it truly offers unlimited servers and sessions, but I'd need to factor in the cost of the agents themselves, which isn't included. I would sign up for the free trial to test its integration with my existing workflow and see if it simplifies tasks without adding complexity.

Simulated interest: 60/100

Amaya van den Heuvelneutral

Initially, the concept of running coding agents on my own server is appealing for data privacy, which is important. The ability to manage tasks from my phone is also a plus, especially for quick checks while commuting. However, the page doesn't clearly articulate the setup process beyond mentioning it installs itself. I'd also need to understand how it integrates with existing workflows and what the actual time savings are compared to using these tools directly on my development machine. The pricing is also a bit unclear – it mentions $29.99/year or $2.99/week for Maude itself, but then states each agent requires its own account and plan. I'd want to sign up if the setup is as seamless as advertised and if it genuinely streamlines my development process without requiring significant overhead or additional costs beyond the agent subscriptions I might already have.

Simulated interest: 40/100

Ed Grimesneutral

The core concept of running coding agents on my own server and controlling them from my phone is intriguing, especially the "nothing to install" part for the server setup. That addresses a pain point for me with managing environments. However, the page doesn't clearly explain *how* it installs itself on the server – is it a Docker container, a script, or something else? I'd also want to know more about the security implications of the server dialing out to Maude's relay. The pricing model is a bit confusing; it says $29.99/year or $2.99/week, but then mentions "each agent still needs its own account or API key." So, is that $30 for the Maude app itself, on top of my existing Claude Pro and ChatGPT subscriptions? If so, that's a bit steep. I'd sign up for the 7-day free trial to test the server setup and see how seamlessly it integrates with my existing tools, but I'd need more clarity on the total cost and security before committing.

Simulated interest: 60/100

Bhudev Iyernegative

The core idea of running coding agents on my own server and controlling them from my phone is interesting, especially the "no setup" part which sounds too good to be true for someone who prefers to tinker. My main hang-up is the pricing. It says "Each agent still needs its own account or API key (for example a Claude Pro or Max plan, or a ChatGPT plan for Codex)" and then lists $29.99/year for Maude itself. I'm used to free tiers and local models, so paying for Maude on top of the agent subscriptions feels like a lot. I'd need to see a clear, quantifiable benefit over my current setup to even consider signing up, and honestly, the idea of paying for a service that just wraps around other paid services isn't very appealing. What would make me sign up is if it offered a way to manage my existing free tier usage or dramatically simplified local LLM integration.

Simulated interest: 20/100

Walgierz Fijałkowskineutral

The core concept of running multiple AI coding agents on my own server and controlling them from my phone is intriguing. It addresses the need for persistent execution, which is a definite plus. However, the setup process, while described as "no setup," still involves pointing it at a server and running a curl command. I'd need to understand the specifics of what "Maude sets itself up" entails and if it truly abstracts away all the complexities I'm used to dealing with in server environments. The idea of approving permission prompts from my phone is convenient, but I'm concerned about the potential for constant interruptions, especially when I'm deep in debugging or focused on a critical task. The pricing model of $29.99/year seems reasonable for the functionality, but I'd need to factor in the cost of the server itself and the individual agent subscriptions. What's unclear is how seamlessly it integrates with existing Python/TypeScript projects and if it can truly assist with the kind of flaky test debugging I spend so much time on. I'd likely leave if the initial setup proved more complex than advertised or if the mobile interface felt clunky for reviewing diffs and commits.

Simulated interest: 40/100

Yvonne Petterssonneutral

The concept of running multiple coding agents on my own server and controlling them from my phone is intriguing, especially the "nothing to install" part for the agents. It sounds like it could streamline my workflow for LogFlow. What's a bit unclear is the exact setup process for the server itself – while it says "Maude installs itself," I'd need to understand the prerequisites for the server. The pricing is reasonable, and the ability to manage tasks remotely appeals to me, especially when I'm away from my desk. I'd consider signing up for the free trial to test how seamlessly it integrates with my existing setup and if it genuinely saves me time on development tasks and refactoring.

Simulated interest: 60/100

Keep exploring.

Find your next question or see which topics divide AI panels.

Keep exploring

What would you ask next?

Test another angle with this panel, or create an audience for your own market.