Forms and surveys decision

LimeSurvey Cloud

A capable developer can build a useful hosted-survey replacement, but reproducing the full hosted product experience (managed SLA, partner services, integrations, polished UI) is larger and would take more work than a narrow self-hosted workflow.

Visit website
SubscriptionCustom pricing
Initial build80 hours
Monthly upkeep8 hours + $0
Evidence3/3 runs agree

No open-source build does this yet

Nothing published replaces this one, so a replacement starts from an empty file. Here is what it would have to cover.

What a replacement has to do

  • Create surveys, publish them, collect responses, view/export results.

What it still won’t have

  • Hosted SLA, uptime guarantees and managed scaling
  • Managed security patching, backups, and automated upgrades
  • Vendor support and partner services bundled with the cloud product
  • Prebuilt integrations and account management in the hosted offering

What remains hard

  • Product polish and ongoing maintenance
Read the build prompt

First-year cost

No published price

LimeSurvey Cloud does not publish a price we could read, so there is nothing to compare against. What building costs is below.

Money you would actually spend

Keep paying

Subscription price × seats × 12

Build it

AI build APIs + hosting

Time you would spend

What you would spend

What we assumed

The verdict above measures whether you could build it. This one is only about money.

Runnable build prompt

Not run yet
Build a self-hosted survey service using PostgreSQL, a Node.js/Express backend, React for the survey editor/renderer, and Docker for deployment. In scope: user auth (email/password), a survey JSON schema editor with question types (text, multiple choice, file upload), public survey rendering and response submission endpoints, storing responses in Postgres, CSV export API, basic results page with summary charts, Docker Compose deployment, TLS via Let's Encrypt, and automated daily DB backups. Out of scope: enterprise SSO, multi-tenant billing, advanced analytics, and marketplace integrations. Include input validation, error handling, and unit/integration tests for API endpoints and core editor/save/submit flows.
How we checked1 sources · 3/3 runs agreed · evidence score 56

How the score was reached

  • Partly verdict base52
  • 3/3 assessment runs agreed+4
  • Evidence score56

The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time — so the same evidence always produces the same number.

How scoring works →

Cited sources · 1

Every page the run actually retrieved.

Integrity checks

What held up, and what did not.

✓ 3 independent runs, one answer✓ Citations limited to fetched pages! 1 moat recorded