Is your developer license perpetual? Do I need to renew my purchased developer license every year?
The license is perpetual. You get permanent access to the versions released within the first 12 months of the original purchase date. Optionally, you can choose to continue receiving all updates and technical support at any time in the future by paying the annual support fee with a discount of around 60% of the current license cost if your plan is within 2.5 years of expiration, and with a discount of a 10% if it expired more than 2.5 years ago.
How many licenses do I need if I do not know the exact number of end users who will use SurveyJS Creator to create/modify surveys in my application?
Our developer license is royalty-free. We do not charge any royalties for redistribution of our libraries that have been integrated into your applications.
We do not track the number of applications you create using our libraries, nor do we limit the number of end users of SurveyJS Creator or SurveyJS
Dashboard. Even if your application has thousands of end users, you will only need to purchase a license for each developer of the application that
works with SurveyJS libraries, not every user.
Please note that under general conditions, an end user must not be an application developer who uses the API of our libraries to create/modify their own applications. If your end users are software developers, please contact us at email@example.com to discuss an OEM agreement between our companies that grants license(s) to such non-standard end users.
How do I decide on the number of licenses needed for my team? Do I purchase a license for each developer or is one per team sufficient?
We license our software development products on a per-developer basis. So, the answer to this question depends directly on the number of developers working with the SurveyJS product's APIs, implementing their integration, writing components and/or modifying existing ones, etc. The general rule is that the number of seats purchased must be equal to or greater than the number of licensed developers immediately involved in the development of your application(s) using SurveyJS libraries.
Am I allowed to transfer my license(s) to others? If so, what is the procedure for that?
Yes, license holders are allowed to transfer their rights under the
END USER LICENSE AGREEMENT
any individual, business, or government entity.You can grant the rights for the license(s) to
a new license holder(s), and revoke them at any time in the
License Manager section of your Account.
Please note that a new user account will be automatically generated for a new license holder if they are not registered at www.surveyjs.io at the moment of the license assignment. We will notify such license holders of the granted license and send them password setup instructions via email once the license assignment is complete.
We intend to use the SurveyJS libraries for internal purposes only, in application(s) that don’t immediately generate profit. Do we still have to buy the developer license(s), or can we integrate the libraries free of charge?
You are required to obtain a developer license(s) regardless of the purpose of the application you develop and the use cases you need to handle – whether it is an order form for online payment, an event registration form, a patients’ history chart, or anything in between. However, if you represent a nonprofit organization (NPO), please contact us at firstname.lastname@example.org for a special offer.
Do I need to purchase a license to create an application prototype that embeds SurveyJS Creator for demonstration purposes only?
You are allowed to test the functionality of our libraries and decide whether it’s suitable for your needs and requirements before making a purchase.
Am I allowed to use SurveyJS libraries in SaaS solutions?
YES. The license holder can deploy their license(s) to any web server or cloud for use in their web applications, including SaaS (Software as a Service) applications. However, such applications cannot compete with SurveyJS libraries (software development products) by offering a tool for developers to build their own form management system using the same codebase. Please refer to Paragraph 5 of the END-USER LICENSE AGREEMENT for further details.
Do you store survey results and/or any other respondent data in your database?
The Survey JS project was developed with full integration and security in mind.
We want to enable our users to build their own self-hosted form management system and
avoid third-party storage of sensitive data that they acquire from users. So, we do not
natively keep track of any of your data, nor do we have any access to it unless
you write the code allowing us to do so, although we prefer that you do not.
The only information we store about our users is the information they fill in
to generate a quote and the records of licensed developers so that we can later
identify them in the system when they request assistance.
We strongly encourage our users to store all data using cloud storage facilities of their choice or maintain it on their own premises, instead of using black box SaaS platforms that lock users into an ecosystem they cannot control and put at risk of hacking respondents’ personal data (a large TypeForm’s data breach in 2018 or phishing attacks using Cloud-based survey software in 2020 are good examples).
Do you charge users for storing survey results and/or survey definitions if they don’t have or are not willing to use their own storage facilities?
No, we do not. It’s important to clarify here that the Free Survey tool was created as an MVP(minimum viable product) that demonstrates the capacities of our libraries; unlike other survey platforms, we do not sell cloud storage services or limit the number of forms and submissions per month.The Free Survey tool enables our users to explore the functionality of our libraries and estimate the value they deliver before actually developing their own self-hosted survey software and having those libraries integrated into their application(s). The survey results and definitions created during such tests/trials are saved in Azure storage free of charge.
How do I get the source code of your libraries?
All of our libraries are open-source. You can find the source code and the development history of a library on the SurveyJS GitHub page (choose the library-related repository). You can also view the Issue tab of a library’s repository to check out the bug fixes and new functionality in progress.
Am I allowed to make changes to the source code?
You certainly are. You simply need to select the library-related repository on the SurveyJS GitHub page, create a new branch, and make the required changes.However, we strongly recommend that you contact us about the functionality you want to introduce.It’s possible that the desired functionality already exists or will soon be implemented.We are always happy to collaborate on new functionality with our users as well.
Do you fix bugs and/or add new functionality?
We constantly improve our libraries and try to resolve the majority of open issues before starting
to implement any new functionality. We understand the importance of having bug-free libraries.
Being big fans of test-driven development (TDD), we write hundreds of unit tests to detect and
fix bugs at the initial development stage. Since we have plenty of unit tests, functional (E2E)
tests, and CI setup, we can introduce new minor (but useful) updates every week.
Regarding new functionality, the short answer is yes, we do add new features regularly. However, we thoroughly estimate their cost and potential value to our users as well as possible risks they might entail. The general rule is the bigger the value/cost rate of a requested feature, the more likely we introduce it in the foreseeable future. We certainly do our best to deliver changes seamlessly and avoid any code-breaking changes. Our Survey JSON definition, for instance, created in an early beta version of SurveyJS Creator still works well with the latest versions.
Can I add custom CSS to brand the look of my surveys?
Is it possible to format/style text of survey elements using Markdown?
YES. With SurveyJS you can use HTML and Markdown for common appearance customizations in question titles or values (like making bold/italic or adding images). For advanced scenarios, you can also provide external markdown converter or create custom themes.
Is customization of survey design and its elements free for everyone?
YES. With SurveyJS libraries, you do not need to look up suitable pricing plans to just change theme colors, fonts, or borders – unlimited theme customization capabilities are free for everyone and built-in. Unlike the majority of online survey tools, we do not charge users for such basic capabilities.
How do I remove a referral badge from the footer?
SurveyJS Library and GUI-based Survey Creator do NOT embed any marketing materials into your surveys, including referral badge. So no need to pay extra to hide or turn gray that “Powered by Survey Tool” sign from the footer and the Thank you page at the end of your survey.
Is it true that if I self-host SurveyJS libraries there are no limits on the number of forms I can create, monthly form submissions, and fields per form that I can choose?
YES. SurveyJS does not limit you on the number of survey forms you create (active or inactive), the number and question types you choose to add, as well as the number of responses your users submit in your self-hosted surveys.
Can the SurveyJS Library also be used as a front-end form library, for example, if I need to build a login or an order form?
YES. In addition to using Form Library as an engine that loads survey data to and from a database — allowing you to run all kinds of web forms made with Survey Creator in your app, you can also use it as an extensible front-end form library. Please refer to the SurveyJS cart page to see an example. Almost every element of the page, including the contact information form, the widget itself, and even company details section - all have been built using Form Library.Any SurveyJS form can be modified using the library’s APIs. To communicate with the server, the SurveyJS library uses JSON objects that allow you to separatethe backend from the frontend.So there's no need to develop and support a custom front-end form library if you have SurveyJS.