When LimeSurvey Cloud fits and when self-hosting fits better
LimeSurvey Cloud suits teams that want the vendor to run hosting within a response cap and a chosen region, while self-hosted Community Edition suits teams that need to control server location, plugins and upgrade timing. The deciding inputs are three: how many responses you collect, which data residency rules bind you, and how much patching capacity your team has. If your projects stay under the plan limits, your residency requirement is met by a supported region, and nobody on your side wants to own PHP and database upgrades, Cloud is the simpler choice. Confirm the current region list and the data processing terms with LimeSurvey before you commit, since the pricing page is the source you will rely on for both.
Cloud tends to win for a research group or compliance team with steady, moderate volumes and a single EU region requirement. The Basic, Expert and Business tiers are capped by responses per month or per year and by admin count, so a study that spikes past its cap forces an upgrade or a wait. Self-hosting tends to win when response volumes are large or unpredictable, when you need a specific plugin or server-side customization, or when a data protection review requires the database and uploaded files to sit in infrastructure you already audit. The cost of self-hosting is mostly staff time: someone must track the LimeSurvey release calendar, keep PHP and the database within supported versions, take backups and test upgrades before they go live.
Before choosing, ask LimeSurvey for written answers on what happens to exported data and collected responses if a subscription lapses, and map those answers to your retention policy. The pricing page says an expired account falls back to a Free package and keeps access to collected responses, but your own exit plan should still include a regular export. If you self-host, the equivalent risk moves to you: a patch window you miss can leave a survey platform exposed. Write down who owns each task, how often you export, and how you will move from one model to the other if your volumes or rules change.
How the two models compare on license, limits, data location and upkeep
This table sets LimeSurvey Cloud beside a self-hosted Community Edition install on the factors that usually decide the choice. Read each row against your own response volume, residency requirement and capacity to patch PHP and the database, then confirm current Cloud figures on the pricing page before you budget.
| Factor | LimeSurvey Cloud | Self-hosted Community Edition |
|---|---|---|
| License | Cloud is a subscription service, so the GPL terms cover the software but you license access to the hosted service | GPL v2.0 with the option of any later GPL version, so you can run, modify and redistribute the code under those terms |
| Current stable and support status | The vendor runs the platform, so confirm which version is live and when it changes in your plan terms | Community 7.6.0 is the latest stable release; 6.17.19 reached end of support on August 31, 2026, so older installs need an upgrade plan |
| Response limits | Basic allows 1,000 responses per month; Expert allows 10,000 per year; Business allows 50,000 per year; Corporate is by quote | No response cap from the software itself; capacity depends on your server, database and survey design |
| Pricing and currency | Cloud checkout is in euros; confirm current plan prices on the LimeSurvey pricing page before budgeting | No vendor subscription fee for the software; you pay for servers, storage, staff time and any outside support |
| Hosting regions and data location | Germany, Finland, the UK, the USA, Canada and Australia; Germany or Finland is recommended for EU customers | Survey data stays on the server you choose, including inside your own EU data center or air-gapped network |
| PHP and database requirements | Handled by the vendor; confirm the PHP and database versions in use and the timing of changes | PHP 8.1.29 or later with mbstring and PDO drivers; MySQL 8.0, PostgreSQL 14, MariaDB 10.3.38 or MSSQL 2019 or later |
| Patching and upkeep | Vendor-managed platform updates; confirm maintenance windows and how you are notified | Your team or provider applies PHP, database and LimeSurvey updates and tests plugins such as ExportR after each change |
| Lapse behavior | When a subscription expires, the account falls back to the Free package and keeps access to collected responses | No subscription to lapse; continuity depends on your own backup and retention process |
What data location and access mean for EU research and regulated teams
For EU research and regulated teams, the first question is where responses live and who can reach them. The cards below separate the questions that LimeSurvey Cloud answers through its vendor from the ones a self-hosted install leaves with your own team.
Where responses are stored
On LimeSurvey Cloud, hosting regions include Germany, Finland, the UK, the USA, Canada and Australia, and Germany or Finland is recommended for EU customers. Confirm in writing which region your account and backups use. On a self-hosted install, storage sits on the server you choose, so the location is whatever your data center or cloud account provides. Record the region for every instance, including test copies.
Who holds administrative access
On Cloud, the vendor operates the servers, so your administrators manage surveys and users while the provider manages the platform layer. Self-hosting puts operating system, database and PHP access with your staff or your chosen provider. Write down who holds root, database and backup credentials, and how those roles are reviewed.
Audit and logging ownership
Decide who owns web server, database and application logs, how long they are kept, and where they are exported. A self-hosted install gives you direct access to these logs, but you must configure and retain them yourselves. On Cloud, ask the vendor which logs it keeps, for how long, and whether you can obtain them during an assessment.
Sub-processor and contract questions
Ask the vendor for its current list of sub-processors, the contractual data processing terms, and the breach notification commitments. Confirm whether backups or support staff sit outside the chosen region. Self-hosting shifts these questions to your own hosting provider, so review that provider's terms as carefully as you would a SaaS vendor's.
Evidence a compliance assessor will request
Assessors typically ask for data flow diagrams, access listings, change records, backup test results and the vendor or provider documentation behind each control. A Cloud customer collects much of this from the vendor. A self-hosted team must produce it from its own systems. DeployOpen can prepare controls and evidence for an assessment, but it does not issue audit reports or certifications, which independent auditors and certification bodies provide.
Plan lapse and data retention
When a Cloud subscription expires, the account falls back to the Free package and keeps access to collected responses. Confirm the retention period, export options and the date on which any change takes effect in your contract. On a self-hosted install, retention follows your own backup and deletion policy, so write the schedule into your data management procedures before the first survey launches.
What PHP and database upkeep means when you run LimeSurvey yourself
If you self-host LimeSurvey Community Edition, your team owns the PHP runtime and the database engine under it, and both have version floors you must keep above. LimeSurvey requires PHP 8.1.29 or later with the mbstring and PDO drivers enabled, and it requires MySQL 8.0, PostgreSQL 14, MariaDB 10.3.38 or MSSQL 2019 or later. Those floors are minimums, not a schedule. Each time LimeSurvey raises its requirements, or an upstream PHP or database branch leaves its own support window, your team has to plan a runtime upgrade, test the survey engine, and then move the application. Keep a written inventory of the PHP build, extensions, database engine and version, and the web server, with an owner for each, so that a change in any one of them does not surprise the people running surveys.
With LimeSurvey Cloud, the vendor carries that upkeep, and your team's job shifts to confirming how and when it happens. The Cloud pricing page describes hosted plans and regions, but the facts available here do not state which PHP or database versions Cloud runs, how quickly it adopts new ones, or how security patches are scheduled. Before you choose Cloud for research that must stay on a fixed stack, ask the vendor in writing for its current PHP and database versions, its upgrade and deprecation policy, how much notice it gives before a change, and whether maintenance windows are announced and where. Also ask whether you can pin a survey to a version during a study, since a mid-study platform change can affect data collection and export.
Self-hosting also means you need a patch cadence that matches LimeSurvey's release pace, not just your operating system's. LimeSurvey Community Edition 7.6.0 is the latest stable release, and 6.17.19 reached end of support on August 31, 2026. A team that stays on an older branch after its end of support date runs without upstream fixes, so build a check into your change calendar that compares your installed version against the community downloads page at a set interval. Test each upgrade on a copy of the production database with real survey structures, because schema changes and plugin compatibility are where self-hosted upgrades usually fail. If your team cannot staff that work, a quoted scope from an implementation partner can cover upgrade planning, testing and backup verification, but the work and its cost recur with every release you adopt.
What your team runs in each hosting model
This table sets out which tasks fall to your team when you self-host LimeSurvey Community Edition and which fall to LimeSurvey when you use LimeSurvey Cloud. Read each row as a question to answer before you pick a model, and confirm the vendor's current terms for anything marked for confirmation. The main takeaway is that self-hosting moves operational duties to you, while Cloud moves them to the provider but shifts some decisions about data location and plan limits onto your contract.
| Task | Self-hosted Community Edition | LimeSurvey Cloud |
|---|---|---|
| Server and PHP runtime patching | Your team patches the operating system, web server and PHP runtime. LimeSurvey requires PHP 8.1.29 or later with mbstring and PDO drivers. | LimeSurvey operates the servers and runtime. Ask the provider how and when runtime changes are applied to your plan. |
| Database backups and restores | Your team schedules backups for MySQL 8.0, PostgreSQL 14, MariaDB 10.3.38 or MSSQL 2019 or later, and tests restores. | Ask the provider what backups exist, how long they are kept, and how you would request a restore. |
| Plugin compatibility (ExportR, ExportSTATAxml and others) | Your team tests each plugin against every LimeSurvey and PHP upgrade before rollout, since plugin changes can break exports. | Confirm which plugins are available on your plan, and whether the provider tests them against platform updates. |
| Version upgrades and the 6.x end-of-support lesson | Your team tracks releases. Community 6.17.19 reached end of support on August 31, 2026, so older installs need a planned move to a supported release. | The provider moves your account to supported versions. Confirm the upgrade schedule and whether you can delay a change. |
| Monitoring and capacity for response volume | Your team watches disk, database growth and PHP limits, and sizes the server for your peak response load. | Plans are capped by responses (Basic 1,000 per month, Expert 10,000 per year, Business 50,000 per year). Confirm overage handling before launch. |
| Incident response | Your team investigates, contains and communicates any outage or data incident, under your own runbook. | Ask the provider for its incident process, notification commitments and support hours in writing before you rely on them. |
| Data location and hosting region | You choose the server location, so you control whether EU research data stays in the EU. | Choose a region when you sign up. Germany or Finland are recommended for EU customers, so confirm the region in your contract. |
| Data export on exit | Your team exports responses and survey structure from its own database and storage, on its own timetable. | If a subscription expires, the account falls back to the Free package and keeps access to collected responses. Ask how a full export works before you leave. |
Which features depend on the hosting model
For most research and feedback work, the question tools themselves do not depend on where LimeSurvey runs. The platform supports more than 30 question types and multilingual surveys in more than 80 languages, so a survey designed on Community Edition and a survey designed on a Cloud plan can look and behave the same to respondents. The hosting model mainly changes who operates the instance and how much capacity you control.
- Question types and languages: The feature set is part of the software, so both models offer the same core question library and language support.
- Response volume: Self-hosting has no response cap set by a vendor plan. Cloud plans cap responses, with Basic at 1,000 responses per month and Expert and Business at annual limits.
- Admin seats: Cloud plans limit admin users by tier (1 on Basic, 3 on Expert, 5 to 10 on Business). Self-hosted seat counts follow your own account setup.
- Hosting region: Cloud regions include Germany, Finland, the UK, the USA, Canada and Australia, with Germany or Finland recommended for EU customers.
- Upgrades: Self-hosting means you schedule upgrades, while Cloud handles the platform version.
Confirm on the current pricing page which response limits, admin counts and regions apply to the plan you are considering, since these figures change.
Plugins and custom code are where the two models diverge most. LimeSurvey ships with plugins such as ExportR and ExportSTATAxml, and a self-hosted instance lets your team install, review and modify plugin code on the server. That control matters when a study needs a specific export format, a custom theme or a question behaviour the defaults do not cover.
- Self-hosted access: You control the plugin directory, PHP version and extension set, so you can test and pin plugins against your release.
- Cloud limits: Hosted plans do not give you server file access, so custom code depends on what the vendor exposes on your plan.
- Review burden: Custom code on a self-hosted instance becomes your responsibility to patch, test and document through upgrades.
- Licensing: LimeSurvey is licensed under GPL v2.0 with the option to use any later GPL version, which governs how you may modify and distribute code you change.
- Version pinning: Community Edition 6.17.19 reached end of support on August 31, 2026, so a plugin that only works on an old release can leave you on an unsupported platform.
Before committing, confirm with the vendor whether the plan you need permits plugin installation or custom scripts, and which plugins are available on that tier.
Integrations that pull responses into other systems, or that need a database or file path on the survey server, depend on what the hosting model allows. A self-hosted instance lets you connect LimeSurvey directly to your database, network segments and internal services, which suits research groups that must keep data inside a controlled network. Cloud plans instead route integrations through what the vendor provides.
- Direct database access: Self-hosting lets you run scheduled exports or reporting queries against your own database, with the access controls you choose.
- Network placement: An instance inside your network can reach internal analytics or storage systems without exposing them to the internet.
- Cloud integration path: Hosted plans limit connections to what the vendor supports, so confirm the available export formats and API access for your tier.
- Data retention on lapse: When a Cloud subscription expires, the account falls back to the Free package and keeps access to collected responses, but integrations tied to the paid plan may stop.
- Server requirements: Self-hosting requires PHP 8.1.29 or later with mbstring and PDO drivers, plus a supported database such as MySQL 8.0 or PostgreSQL 14, which your team must maintain.
Ask the vendor which API endpoints, export types and webhooks each plan includes before designing a pipeline around them.
How to move surveys and responses between Cloud and self-hosted
This sequence moves surveys, responses and integrations from one LimeSurvey instance to another while keeping question logic and multilingual content intact. It ends with a verified target and a retired source, so no data exists only in one place during the switch.
Retain a full export before any plan change
Before you change, downgrade or let a LimeSurvey Cloud subscription lapse, export every survey structure and all collected responses from the current instance and store the files in your own controlled location. LimeSurvey's pricing FAQ says an expired subscription falls back to the Free package and keeps access to collected responses, but that is the vendor's stated behavior, so confirm it in writing for your account and do not rely on it as your only copy. Done means you can open the export files and count responses against the source dashboard.
Confirm target PHP and database versions
Before installing the self-hosted instance, check the target against the LimeSurvey requirements: PHP 8.1.29 or later with mbstring and PDO drivers, and one of MySQL 8.0, PostgreSQL 14, MariaDB 10.3.38 or MSSQL 2019 or later. Install the current stable release, Community Edition 7.6.0, rather than an older branch that has reached end of support. Your platform team owns this check. Done means the server reports matching versions and the database accepts connections from the web tier.
Load surveys and responses into the target
Import the survey structures first, then the response data, into the new instance on infrastructure you control. Keep the import in a staging database so the source remains untouched. The person running the import should record which survey IDs map to which new IDs, because integrations and links depend on them. Done means every survey is present, response counts per survey match the source export, and the mapping sheet is saved with the migration record.
Validate question logic and multilingual content
Test each survey against the source, not just its appearance. Walk through conditional branches, validation rules, equation fields and required questions, then check that every language version renders the same text and options. LimeSurvey supports more than 30 question types and surveys in more than 80 languages, so sample at least one path per language. A survey researcher should sign off each instrument. Done means the test log lists each survey, language and path with a pass result, and any gaps are fixed before cutover.
Reconnect integrations and export plugins
Reconnect every consumer of the data: embedded survey links, redirect URLs, reporting exports, and any analysis pipelines that use plugins such as ExportR or ExportSTATAxml. Update hostnames, certificates and API credentials to point at the new instance. Confirm that each plugin is installed and enabled on the target, since plugins are not part of the data export. Done means each integration returns the expected output from a test response.
Plan and run the cutover
Choose a window where no new responses are expected, freeze the source, take a final delta export, and load it into the target. Then switch DNS or links to the new instance and monitor incoming responses for errors. Ask your provider or internal team to confirm the cutover plan in writing, including who can roll back. Done means the new instance receives live responses and the final response counts match the frozen source.
Retire the old instance after verification
Keep the source instance and its exports read-only for a period your data retention policy sets, then decommission it and delete copies you are no longer required to hold. Record the decision, the retention period and the deletion evidence in your change log. For regulated research data, confirm the retention and deletion requirements with your compliance lead before deleting anything. Done means the old instance is offline, the retention record is signed off, and the only remaining copies are the ones your policy permits.
What buyers ask before choosing a hosting model
What drives the cost of LimeSurvey Cloud versus self-hosting?
Cloud cost is a recurring subscription sized by responses and admin users, so volume and team size set the price. Self-hosting Community Edition has no license fee, but the organization pays for servers, PHP and database upkeep, backups, upgrades and staff time. The published Cloud tiers are Basic at 1,000 responses per month with 1 admin user, Expert at 10,000 responses per year with 3 admins, and Business at 50,000 responses per year with 5 to 10 admins, while Corporate is quoted (LimeSurvey pricing page). For a quote, ask for the response cap, admin count, hosting region, support terms and the cost of exceeding the cap. For a self-hosted option, ask for the scope of any partner work, which should be fixed and written before work starts.
Can a team run a self-hosted LimeSurvey without outside help?
Yes, if the team already runs PHP applications and a supported database and can keep them patched. LimeSurvey Community Edition is free under GPL v2.0 with the option of any later GPL version, so the software itself carries no license cost. The work is operational: installing the application, configuring PHP with mbstring and PDO drivers, maintaining the database, applying updates and running backups. Confirm the current version requirements against the LimeSurvey GitHub repository before you build. Teams without that skill set, or without a secondary person to cover updates, often find outside help easier to justify than a Cloud subscription.
How long do a self-hosted setup and data migration take?
No researched figure is available for setup or migration duration, so confirm it with your own environment and any implementation partner before you commit. The duration depends on the number of surveys, the size of the response history, custom plugins or themes, the target PHP and database versions, and how much integration testing your compliance team requires. Ask for a written plan that lists each phase, its deliverables and the acceptance tests. Also ask how existing Cloud or on-premise data would be exported and verified, because response data is the part that cannot be rebuilt.
What does a self-hosted LimeSurvey need from internal staff?
Plan for a named owner for the platform, someone who handles PHP and database maintenance, and a backup and restore routine that has been tested. Security work includes applying application updates, reviewing access for admin users, and keeping TLS, logging and network controls in line with your policies. Staff also need to track the release calendar, because older community releases lose support. The older 6.17.19 release reached end of support on August 31, 2026, while 7.6.0 is the latest stable release (LimeSurvey community downloads page). Confirm your internal coverage for holidays and absences, since a single administrator is a common single point of failure.
What happens to survey data if a LimeSurvey Cloud plan lapses?
When a Cloud subscription expires, the account falls back to the Free package and keeps access to collected responses (LimeSurvey pricing page FAQ). That protects the data you already hold, but it does not restore the plan's capacity, admin seats or any features the lapsed plan included. Before you rely on this, confirm in writing what the Free package allows, how long data stays available, and how you export responses in a usable format. Build an exit routine that exports responses and survey structures on a schedule, so you are never dependent on a single account state.
Which LimeSurvey Cloud region should an EU research team choose?
Choose Germany or Finland for EU research, because the LimeSurvey pricing page recommends these regions for EU customers. Cloud hosting is also offered in the UK, the USA, Canada and Australia, which may suit other research programs but needs a separate data location review. Confirm with your data protection officer and ethics board which jurisdictions your participant consent forms and data processing agreements allow. Ask the vendor to confirm where backups are stored, which subprocessors touch the data and how deletion requests are handled. A self-hosted deployment inside your own EU infrastructure gives you direct control of location, but it moves those obligations onto your team.
When does Corporate or a self-hosted partner make sense?
Corporate makes sense when the response volume, admin count or hosting requirements exceed the published Business tier and you need a quoted agreement. A self-hosted partner makes sense when you want LimeSurvey inside your own cloud account, data center or air-gapped network but lack the staff to run it. DeployOpen plans, implements, hardens, backs up, upgrades and supports self-hosted open-source platforms inside the client's infrastructure, and most engagements are fixed-scope with scope and deliverables agreed in writing before work starts. DeployOpen does not issue compliance certifications, so any assessment still depends on an independent auditor. Ask for a written scope and a quote that follows from it.
How DeployOpen scopes, deploys and supports self-hosted LimeSurvey
DeployOpen plans, implements, hardens, backs up, upgrades and documents self-hosted open-source platforms inside the client's own infrastructure, so a LimeSurvey install runs in your cloud account, data center or air-gapped network. We start from where your survey data must live and who will operate the stack, then work through the options in writing before any build begins.
How we scope
- Written scope that names the survey types, languages and respondent volumes the install must handle.
- Data residency requirements for EU research, including which hosting location and provider the data will use.
- Confirmation of the PHP, database and web server versions your team will support, checked against the current LimeSurvey requirements.
- Engagements are fixed-scope, with deliverables and timelines agreed in writing before work starts.
How we build
- Installation of LimeSurvey Community Edition on your infrastructure with the PHP extensions and database engine named in the scope.
- Configuration of authentication, backups, file storage and any plugins your research team needs, such as the ExportR or ExportSTATAxml exports.
- Security testing of the deployed application and its hosting layer, reported with findings and remediation steps.
- Documented upgrade path so the team can move to a newer LimeSurvey release before an older one leaves support.
How we hand over
- Runbooks covering installation, backup and restore, upgrades and rollback, written for the team that will operate the platform.
- Evidence packs describing configuration, access controls and data flows for your internal reviewers or external assessors.
- Knowledge transfer sessions with the administrators who will own the platform after handover.
- Clear records of what DeployOpen configured and what your team remains responsible for going forward.
How we support
- Ongoing support, upgrades and continuous testing are available as a retainer, scoped in writing.
- Upgrade planning tied to LimeSurvey release and end-of-support dates, confirmed against the vendor's published information at the time.
- Periodic retesting of the deployed instance after major changes to plugins, hosting or PHP versions.
- Ask any provider, including us, to confirm in writing who patches the PHP runtime, database and operating system.
