Buy and Use with Confidence
All SurveyJS products come with a 90-day unconditional money-back guarantee.
We license our software libraries per developer. You also get permanent access to the version released in the first 12 months since your original purchase. To continue to receive updates and technical support, you can renew the license and receive around 60% discount. Please refer to our License page for more information on our license.
Use the comparison table below to learn more about our products. If you have any questions or require assistance, email us email@example.com.
Best ValuePro (All products)
899 EUR / 1079 USD
Creator / Builder
499 EUR / 599 USD
499 EUR / 599 USD
199 EUR / 239 USD
Allows end-users to create or edit the survey / form definition.
Helps you to create pages with survey / form results. It contains charts, a wordcloud, tables, and other widgets that visualize survey results.
Allows you to export survey / form results into PDF form.
Renew today and stay up to date with the latest products and features and continue getting the technical support.
Is your developer license perpetual? Should I renew my purchased developer license every year?
The license is perpetual. You get permanent access to the version released in the first 12 months since your original purchase. A license renewal is optional and you can do it any time in the future. To continue to receive updates and technical support, you can renew the license for another 12 months and receive around 60% discount.
How many licenses do I need? I do not know the exact number of end users who will use SurveyJS Creator to create/modify surveys.
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 care how many applications you create using our libraries. As well, we do not care how many end users of SurveyJS Creator or SurveyJS Analytics Pack you have. This means that if you have dozens of millions of end users, then you are making great and cool apps and we are proud that you choose our software for your product(s).
A more accurate license-related question that you need to ask yourself is: How many software developers in my company/team are going to work with SurveyJS product APIs, integrate them into your applications, write components and so on? The answer to this question will give you the correct number of licenses to purchase.
Note that it is implied that your users are exactly end users - they are not application developers by themselves and they do not use the API of our libraries to create/modify their own applications. In case you create software for software developers, please contact us to make an OEM agreement between our and your companies to license such developers.
How does the license transfer process work?
To transfer a license, you need to send a recipient's email address to firstname.lastname@example.org. We ordinarily do the transfer in the same day. Note that the recipient should be registered within our system using the provided email address.
Our app is not used for making money. Will SurveyJS Creator, SurveyJS PDF Export and SurveyJS Analytics Pack modules be free for us?
We are going to use your libraries in our internal app, is it free for us?
Do you save our user responses and survey results onto your service? What information do you store in your database?
The idea of our project is to allow other companies to get rid of using third-party survey services and create their own survey app/service. If you use our libraries in your web applications, then we do not touch your data unless you take some extra actions and write specific code allowing this. By default, we do not have access to your data.
We do not have any intention to get your data and we prefer not to. The only information that we need to store is the information needed to create the invoice and minimum information about your software developers to arrange licenses for them in our system.
We do have our own survey cloud. It is free. We created it as an example that demonstrates what can be done with our client libraries. It allows you to start and test the functionality of our libraries quickly, without creating your own services and databases.
Do I need to purchase a license to create a proof-of-concept application that embeds SurveyJS Creator for demonstration purposes?
You can try our libraries before a purchase. We allow you to purchase our software after you make certain that it works as needed.
How to get your source code?
All our libraries are open source software. You can find our source code on GitHub. Please select a library-related repository to get the library's source code and development history. In repositiries, use the Issues tab to track our progress in fixing bugs and implementing new functionality.
Could I change the source code?
Absolutely. You can fork our GitHub repository and make the required changes. However, we strongly recommend that you contact us about the functionality you want to introduce. Probably, this functionality might be already implemented or we might be going to introduce it in the short term. And we always are open to work together on any required functionality.
Do you fix bugs and/or add new functionality?
We constantly improve our libraries. We are trying to keep the number of bugs at the minimum possible level and to fix open issues before starting to work on any new functionality. We understand the importance of having bug-free libraries. Being big fans of test-driven development (TDD), we massively write unit tests to reproduce bugs at early development stages and to be able to fix issues as soon as possible.
Since we have a lot 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. However, it depends. Every new functionality/feature has its value and cost. By value, we mean how useful it is for our customers. How many users are going to use it? Is it crucial for them to have it? By cost, we mean developer hours, the possibility of breaking changes, the harmfulness of breaking change if any introduced. We do not like breaking changes, nobody likes them. As an illustration - our Survey JSON definition exists from the first beta and still works perfectly in the current version. So, if a feature's value/cost rate is high, we will likely introduce the feature. The bigger the rate is, the sooner we will work on the feature. And, on the contrary, if the value/cost rate is low, then we will unlikely introduce the functionality in the near future, probably never.