Managed LimeSurvey hosting
Pilae installs, patches, backs up and monitors LimeSurvey for you, on your own servers or in any of 10+ Pilae Cloud regions, six of them in Switzerland and the EU.
From CHF 449EUR 479USD 559 a month on Starter, hosting and onboarding included.
- Workflow and data
- Open source
- Replaces SurveyMonkey
- Runs on
- Your own hardware, or a Pilae Cloud region
- Replaces
- SurveyMonkey, Qualtrics, Microsoft Forms
- Licence
- GPL-2.0-or-later
LimeSurvey among the workflow and data apps
The automations and dashboards a department builds for itself, running where the data already is instead of where a SaaS keeps it.
LimeSurvey system requirements
Before anything is deployed, this is what has to exist. We size it with you in the first session, and we say so when your own hardware is already enough.
All 5 requirements, and why each is there
- CPU and memory2 vCPU · 4 GBOur starting size for PHP-FPM and the database together. LimeSurvey wants at least 256 MB per PHP process, and up to 512 MB where PDF exports are used.
- DatabaseMariaDB, InnoDBUpstream supports MariaDB, MySQL, PostgreSQL and SQL Server, and we use MariaDB. Every activated survey gets its own response table with a column per answer field, so we test the longest questionnaire against it before launch.
- MailSMTP relay, SPF, DKIMInvitations and reminders are sent from your domain. Without SPF and DKIM for it, a large invitation run lands in spam.
- File storageVolume for upload/Holds the files respondents upload, images in questionnaires, your survey theme and plugins. A response that points to a missing file is an incomplete response.
- Staff sign-inOIDC proxy or LDAPThe Community Edition authenticates against its own users, LDAP, or the web server in front of it. An OpenID Connect proxy in front of the administration is how Keycloak or Entra ID reaches it.
Running LimeSurvey in production: what it takes
Pin and deploy on InnoDB
A LimeSurvey release we have run, on PHP-FPM, with MariaDB on InnoDB rather than the installer's MyISAM default, so a backup taken while responses arrive is consistent.
Publish the surveys, keep the admin private
Survey pages go out through the Pilae gate on port 443 so respondents can reach them. The administration answers only on your private network, behind Keycloak or your own identity provider.
Send invitations through your relay
Invitations and reminders leave through your SMTP relay under your domain, in batches the relay accepts, with bounces going to a mailbox somebody reads.
Back up the data, the files and the keys
The database, the upload directory and the key file go offsite daily, encrypted. On the Enterprise plan, once a month we restore all three into a scratch instance and open a response with a file attached.
Upgrade around your fieldwork
Releases arrive often and can change the database schema. The Pilae Agent tests each upgrade on a copy with your surveys and theme, waits for your approval and applies it in your window. Major versions are scheduled between fieldwork periods.
From our runbook
What a LimeSurvey restore needs
mariadb/limesurveyInnoDB, 6.2 GB
- lime_surveyssurvey settings
- lime_responses_482915one table per active survey
- lime_tokens_482915participants, name and email encrypted
- lime_timings_482915time per page, if recorded
- lime_old_responses_317204_20260612093015kept when a survey was deactivated
upload/14 GB
- surveys/482915/filesrespondent uploads
- surveys/482915/imagesimages in the questionnaire
- themes/survey/acmehouse survey theme
- pluginsinstalled from the admin
application/config/
- config.phpdatabase connection and URL format
- security.phpencryption keys, generated once
- s3://acme-backupsoffsite, daily, encrypted
Migrating from SurveyMonkey to LimeSurvey
SurveyMonkey exports responses as CSV, XLS or SPSS files. The questionnaire itself downloads as a PDF, and its API returns the design as JSON, but LimeSurvey imports neither, so surveys are rebuilt. That is less work than it sounds: LimeSurvey imports a questionnaire from a tab-separated file, so a long survey can be written in a spreadsheet rather than clicked together. Logic is the real work. Skip logic and piping become LimeSurvey conditions and expressions, and quotas become LimeSurvey quotas. Questions cannot be added or removed once a survey is collecting answers, so every branch is tested before activation. Past results stay in those export files. Benchmarks against other SurveyMonkey customers, and integrations built on its apps, do not come across.
- CompareSelf-hosting vs managed open source: doing it yourself, or PilaeSelf-hosting gives you the apps and the whole job of running them. Pilae gives you the same open-source apps, operated under a contract, on your premises or in Pilae Cloud.
Moving from SurveyMonkey to LimeSurvey, step by step
- Sort live surveys from finished ones: Which surveys are running, which recur every year, and which only need their results kept. Finished surveys are exported and archived, not rebuilt.
- Rebuild the questionnaires: Long questionnaires are written in LimeSurvey's tab-separated format and imported. Skip logic becomes conditions, checked with LimeSurvey's logic check before anyone sees the survey.
- Bring the participant lists: Participant lists are imported into each survey from CSV or an LDAP query, with encryption switched on for names and email addresses.
- Test every branch, then swap the links: Test responses go through each branch, quota and email before activation. Links on the intranet and in newsletters are replaced before the old account closes.
What LimeSurvey is, and who runs it
Surveys and research questionnaires with personal invitations and anonymised responses, run in Switzerland, the EU or your own datacentre so the answers stay in your jurisdiction.
Self-hosted LimeSurvey for research and public-sector surveys
LimeSurvey is an open-source survey platform. It handles branching logic, quotas, many languages in one survey, personal invitation tokens or a public link, and exports to SPSS, R and Stata. It is used in universities, research projects and public administrations, and it covers most of what those teams use SurveyMonkey or Qualtrics for.
We run it where your data-protection assessment says the answers may be kept: on your own hardware, or on a dedicated machine in Zurich, in one of the five EU Pilae Cloud regions or in one of six further afield. For a research project, an ethics application asks where the answers are stored, and the answer is a place you can name.
Read the full briefFold the brief
LimeSurvey in production: sign-on, invitations and encryption keys
Respondents have to reach the survey, and staff have to reach the administration. We publish survey pages through the Pilae gate on port 443 and keep the administration on your private network, where an OpenID Connect proxy signs staff in through Keycloak or Entra ID. Invitations and reminders go out through your own SMTP relay, under your domain.
We switch on LimeSurvey’s encryption for participant names and email addresses, and its keys live
in security.php. Lose that file and the fields cannot be read back. It is backed up with the
database and the upload directory, daily and encrypted, to an offsite location in the country your contract names, and on the Enterprise plan all three are restored into a scratch instance once a month.
Probes check the survey pages every 60 seconds, and a failure alerts an engineer. The
Pilae Agent rehearses each upgrade on a copy and, once you approve it, applies
it in your window and runs the database update itself, rather than leaving that to whoever opens
the admin page first.
LimeSurvey licence and editions
LimeSurvey is GPL-2.0-or-later, and the Community Edition has no paid feature tier and no fee per response or per user. LimeSurvey GmbH sells a hosted service and a paid updater, ComfortUpdate. We upgrade from the release packages, so your installation does not need the updater. LimeSurvey GmbH’s trademark policy covers the name and logo, not your use of the software. Our operation follows the published plans. Talk to us about your next round of fieldwork.
What Pilae is responsible for
The same commitments on every app we run, LimeSurvey included, and what stays yours. How the platform does it.
Ours
- A pinned version: A version we have run, not whatever latest resolves to that day.
- A runbook: What it depends on, how it fails, what to do about it. In your repository.
- Daily backups: Encrypted and offsite, and on Enterprise restored every month. A backup nobody has restored is a file.
- A patch window: Security updates in a window you agreed, with a rollback ready.
- Someone watching: Every endpoint probed on the minute. An alert reaches a person, not a dashboard nobody opens.
Yours
- The credentials: You hold them. Ours are separate, named, logged and revocable with one command.
- The approval: We ask before anything changes outside an agreed window.
- The exit: The machine, the data, the compose files and the runbook are already yours. Nothing stops when our access does.
Who runs it
Engineers who answer for it
Our engineers review every plan the Pilae Agent prepares and answer for the result.
Your data stays where the contract says
On your own servers or in Pilae Cloud. On Business and Enterprise you choose the region, and your contract names each location.
A Swiss company, a Swiss contract
Pilae is a Swiss company, and your contract with it is governed by Swiss law.
LimeSurvey runs on Starter from CHF 449EUR 479USD 559 a month in Pilae Cloud, or on Business with up to three apps on your own servers.
Compare the plansLimeSurvey: common questions
Is LimeSurvey open source?
Where do the responses live?
Can responses be anonymous?
Can LimeSurvey replace Qualtrics?
Why not use LimeSurvey Cloud?
Ask the engineers who would run your LimeSurvey
Thirty minutes on the deployment you already have, or the one you are about to start.
- Go deeperPrivate AI and research data platforms for universities and research labsPrivate AI, research databases and collaboration for universities and labs, on your servers or in Switzerland, operated with every change approved and recorded.
- CompareWorkflow and data appsThe automations and dashboards a department builds for itself, running where the data already is instead of where a SaaS keeps it.
- CheckSecurity for self-hosted open-source apps, run by PilaePrivate networking, hardened machines, named access, tracked advisories and a full audit log, built to ISO 27001 controls.
