LimeSurvey Hosting
Build and run advanced surveys with logic, quotas, multiple languages, and detailed statistics.
- One click deploy
- 1 GB RAM Memory needed
- 15 GB Disk Space Needed
- From 2 € Price
Official links
LimeSurvey’s official links and original website
LimeSurvey Website
More
Tech
- Docker image
- martialblog/limesurvey:latest
- Default port
- 8080
- Database
- mariadb
How LimeSurvey works
Survey administrators create question groups, choose question types, define validation, and use conditional logic to decide which questions a participant sees. Responses are stored in MariaDB and can be reviewed, filtered, exported, or analysed after collection. Surveys may be anonymous or tied to a participant table depending on the selected settings.
Quotas stop or redirect respondents after a defined condition is reached, while tokens can restrict access to an invited list. Multiple languages can share one survey structure. The catalogue creates an administrator account during deployment, avoiding an open first-run claim screen.
Key LimeSurvey features
A broad question library covers single choice, multiple choice, text, ranking, arrays, numerical input, dates, files, and other formats. Relevance expressions, piping, validation, and branching support complex research designs without requiring every participant to follow the same path.
Themes control presentation, and response exports support further analysis in external tools. Email invitations, reminders, confirmations, and token distribution are common upstream workflows, but application email is disabled on AvaHost, so those messages cannot be sent by the hosted installation.
LimeSurvey vs SurveyMonkey
LimeSurvey is a self-hosted survey system that gives the operator control over the application, database, participant tables, and configuration. SurveyMonkey is a provider-managed platform combining templates, question logic, response collection, analytics, collaboration, integrations, and vendor-operated infrastructure.
SurveyMonkey may suit teams seeking a guided hosted service with ready-made templates and managed delivery. LimeSurvey is more appropriate for complex conditional surveys, multilingual projects, and direct infrastructure control, provided the organisation can distribute survey access without relying on application email.
Who uses LimeSurvey
Academic researchers build structured questionnaires, schools collect evaluations, associations survey members, and organisations run internal assessments or public consultations. The tool is useful when quotas, branching, multilingual content, or participant-specific access make a basic form builder insufficient.
It is not a substitute for research ethics, sampling design, or legal review. Administrators must decide what personal data is collected, who can access it, how long it is retained, and whether anonymous settings match the actual survey configuration.
Self-hosting LimeSurvey: requirements and cost
Resource demand depends on survey complexity, concurrent respondents, question count, uploaded files, response volume, exports, and administrative analysis. MariaDB stores surveys, participant data, responses, tokens, permissions, and settings. The database is included with LimeSurvey but remains unmanaged, and its memory is outside the exported application minimum.
The corrected minimum is Plan 2 at €5 for the application and MariaDB stack. AvaHost includes one-click deployment, a custom survey domain, automated HTTPS, automatic application updates, and scheduled backups. Application email is disabled, so invitations, reminders, confirmation messages, and email-based token distribution must use another approved workflow.
F.A.Q
LimeSurvey begins at €5 on Plan 2 after including capacity for MariaDB. The hosting service provides a custom domain, automated HTTPS, application updates, and scheduled backups. Survey complexity, simultaneous respondents, uploaded files, participant tables, response volume, and large exports influence whether a larger plan is needed.
AvaHost provisions MariaDB and connects LimeSurvey to it during deployment. Survey definitions, question logic, participant records, tokens, responses, permissions, and settings depend on the database. MariaDB is included but unmanaged, so its contents and any uploaded survey files should remain coordinated during maintenance, migration, export, or recovery.
A custom survey domain can be connected with automated HTTPS after DNS points to the hosted application. Choose the final address before distributing participant links or embedding a questionnaire. Then test anonymous access, token access, branching, file uploads, completion pages, and integrations that may still reference the former hostname.
No application email is delivered from the hosted service. Invitations, reminders, completion confirmations, token mail, and email-based administration workflows are unavailable. Surveys can still be reached through manually distributed links, and participant tokens can be provided through another approved channel. Test the intended distribution process before opening a study to respondents.