PROVIDER - Long-standing open-source survey system

LimeSurvey

Started in 2003 as PHPSurveyor, LimeSurvey is a German-maintained open-source survey system whose GPL licence, conditional logic and quota control keep it a default for academic and internal research.

Form & Survey Germany 2026.11.20
3.8pts

Detailed Notes

Pros 5 items

GPL licensed and in development since 2003 as PHPSurveyor, deployable on your own LAMP stack or through the official cloud
20+ question types cover radio, matrix, ranking, upload and equation questions, with quotas, conditions and assessments in 1 survey
Multilingual support works at survey and question level, 1 survey can carry 80+ language versions, and the respondent language can be matched automatically
Statistics and export cover 4 formats - SPSS, R, Excel and CSV - and produce cross-tabs, basic charts and raw responses
The RemoteControl API exposes JSON-RPC methods, so all 3 jobs - survey creation, participant import and response export - can be scripted in bulk

Cons 4 items

The console keeps a traditional form-system shape, older than commercial SaaS in editor and templates, and mobile usability depends on theme customisation
Self-hosting means owning PHP versions, the database, upgrades and backups, and plugins plus custom themes often break across major upgrades
Cloud tiers cap questionnaire count, responses and some advanced capabilities, and the free tier is only enough for evaluation
Chinese documentation and local support are limited, so complex logic issues are resolved through logs, forums and reproduction

Service Overview

LimeSurvey is a German-maintained open-source survey system that began in 2003 under the name PHPSurveyor and has continued under its current name since. Within the Forms and Surveys category it represents the full survey system route: question types, conditions, quotas, participant management and statistics all live in one console rather than being assembled from integrations.

Two properties carry it. The first is open source and self-hostable: under the GPL it installs on your own server and keeps definitions, responses and uploads in your own database. The second is completeness. Quota control, assessment mode, token-based participant management and 80+ language versions are things short-form commercial tools usually skip, and they are why academic and government research has treated it as the default for years.

The trade-off is a console that looks its age. The interface carries PHP-era design, the editor and templates are less modern than newer SaaS, and mobile usability depends on theme work. It suits teams treating a survey as a research instrument rather than a marketing landing page.

Key Strengths

  • Breadth in one place: Quotas, conditions, assessments, token-based participants and multilingual versions share one console, so rigorous research needs no tool stitching.
  • Data stays with you: GPL self-hosting keeps definitions, responses and uploads in your database, with exports to SPSS, R, Excel and CSV.
  • Solid quota and sampling: Conditional quota limits with termination messages combine with tokens for targeted invitations and one-time submissions, which is the part researchers rely on most.
  • Mature multilingual surveys: Survey-level and question-level translation let one survey carry dozens of language versions, with respondents routed by browser language.
  • Scriptable API: RemoteControl exposes JSON-RPC, so survey creation, participant import and response export can run as batch jobs for recurring studies.

Product Ecosystem

Platform capabilities

The console follows surveys, participants, responses and statistics. Question types span radio, checkbox, matrix, ranking, text, upload, equation and array questions. Logic covers branching, quotas, assessments and validation. Participants use tokens for invitations, tracking and single submissions. Statistics provide frequencies, cross-tabs, charts and response browsing.

Quotas are the most distinctive capability. Limits are set per answer combination, and respondents hitting a full quota see a termination page, which keeps sample structure controllable. Assessment mode maps answers to scores, fitting knowledge tests and scale scoring.

Integrations

The standard pattern is deploying on your own LAMP or LEMP stack and integrating through the RemoteControl API: templates generated by script, participant lists imported from HR or a CRM, responses exported on a schedule into a warehouse. Out-of-the-box SaaS-style integrations are thin, and one-way pushes such as webhooks usually mean writing a plugin or polling the API.

Typical scenarios

Academic studies, government and institutional statistics, employee satisfaction and engagement censuses, course evaluations and exams, and market research needing quota control are the strongest ground. Short-lived marketing forms are not: a visual SaaS is faster for those.

Limitations

  • Traditional interface: Console and editor keep an older interaction model, the template library is limited, and mobile experience depends on theming, which feels heavy on first contact.
  • Real operations overhead: Self-hosting means PHP versions, database, upgrades and backups, and plugins or custom themes frequently break on major upgrades, so long-term maintenance needs dedicated capacity.
  • Cloud quotas bite: The official cloud caps questionnaire count, responses and some advanced features by tier, the free tier is evaluation-grade, and full capability sits in enterprise plans.
  • Community-centric support: Chinese documentation and local support are thin, and complex logic failures require logs, forums and reproduction, which makes resolution time unpredictable.

Use Cases

  • Academic and institutional research (★★★★★): Quotas, sampling, multilingual versions and SPSS/R export are all present, making it the default choice here
  • Employee satisfaction and engagement censuses (★★★★☆): Token invitations with anonymous options balance tracking against privacy
  • Course evaluations and knowledge tests (★★★★): Assessment mode maps answers to scores and multilingual versions serve international programmes
  • Public sector and enterprise with no data egress (★★★★☆): Self-hosting keeps surveys and responses inside the network for audit requirements
  • Short marketing forms and landing pages (★★): Interface and templates are not competitive, and a visual SaaS is faster

Pricing

Item Price Notes
Self-hosted community edition $0 Full GPL source, server, database and operations costs are yours
Cloud free tier $0 Capped questionnaires and responses, some advanced features restricted
Cloud paid tiers Monthly or annual Higher response caps, branding removal and feature unlocks; tiers follow the official site
Enterprise plan Sales quote Advanced quotas, dedicated support and custom terms, usually annual

Prices and quotas follow the official pricing page. Self-hosting looks free but costs servers, backups and upgrade labour: a major upgrade usually needs a maintenance window plus regression testing, and that should be amortised into the annual budget.

FAQ

Is the self-hosted edition feature-limited?

The community edition is complete for surveys, quotas, logic and statistics; restrictions sit on commercially licensed add-ons and official support. The real cost of self-hosting is operations, not missing capability.

How does quota control work?

Set limits for specific answer combinations, and respondents who hit a full quota are shown a termination page or redirected. Quotas are what makes sample structure controllable, so compute per-stratum limits before opening a study.

What is mobile usability like?

The default theme is passable on phones and generally needs a responsive theme or custom CSS. For low-bandwidth and older devices, test long question pages on real hardware before launch.

How does it compare with SurveyMonkey or Qualtrics?

SurveyMonkey and Qualtrics are hosted SaaS with better out-of-the-box experience and support, billed by responses or seats. LimeSurvey is open source and self-hostable with strong quotas and multilingual support, and its cost model is fundamentally different. Pick it when data must stay on your own server, otherwise SaaS is less effort.

Code Examples

Open a RemoteControl session and export responses

#!/usr/bin/env python3
# RemoteControl is a JSON-RPC interface; exchange the session key first and make sure the survey is active
import os
import json
import urllib.request

API = os.environ["LIMESURVEY_API_URL"]      # e.g. https://survey.example.com/index.php/admin/remotecontrol
USER = os.environ["LIMESURVEY_API_USER"]
PASS = os.environ["LIMESURVEY_API_PASSWORD"]

def rpc(method, params, sid=None):
    payload = {"method": method, "params": params if sid is None else [sid] + params, "id": 1}
    req = urllib.request.Request(
        API,
        data=json.dumps(payload).encode(),
        headers={"Content-Type": "application/json"},
    )
    with urllib.request.urlopen(req, timeout=30) as resp:
        body = json.loads(resp.read().decode())
    if "error" in body:
        raise RuntimeError(body["error"])
    return body["result"]

sid = rpc("get_session_key", [USER, PASS])
try:
    surveys = rpc("list_surveys", [None], sid)
    target = surveys[0]["sid"]                        # placeholder: pick the survey you need
    csv_data = rpc("export_responses", [target, "csv", "en", "complete", "long", None, None], sid)
    print(f"survey {target} exported, base64 length={len(csv_data)}")
finally:
    rpc("release_session_key", [], sid)               # always release, or session slots run out

export_responses returns base64-encoded content that must be decoded before writing to disk, and forgetting to release the session key is the most common bug in these scripts.

A minimal self-hosted compose

# Illustrative minimum; check image tags and init steps in the official docs. Community images carry no official SLA
services:
  db:
    image: mariadb:10.11
    environment:
      MYSQL_ROOT_PASSWORD: ${MYSQL_ROOT_PASSWORD}
      MYSQL_DATABASE: limesurvey
      MYSQL_USER: limesurvey
      MYSQL_PASSWORD: ${MYSQL_PASSWORD}
    volumes:
      - dbdata:/var/lib/mysql

  limesurvey:
    image: martialblog/limesurvey:6-apache
    depends_on:
      - db
    environment:
      LIMESURVEY_DB_HOST: db
      LIMESURVEY_DB_NAME: limesurvey
      LIMESURVEY_DB_USER: limesurvey
      LIMESURVEY_DB_PASSWORD: ${MYSQL_PASSWORD}
      LIMESURVEY_ADMIN_USER: ${LIMESURVEY_ADMIN_USER}
      LIMESURVEY_ADMIN_PASSWORD: ${LIMESURVEY_ADMIN_PASSWORD}
    ports:
      - "8080:8080"

volumes:
  dbdata:

Inject database credentials and the admin account from .env, change the default admin password immediately after initialisation, and confirm whether /admin is restricted by source IP.

Community & Resources

Official channels

Learning resources and tools

Visit LimeSurvey Website → https://www.limesurvey.org/
Visit Website ↗