Hello Dataverse,
I want to know all type of fee using dataverse and supporting during installation.
Hi @saroth ! I hope you didn't come here for Microsoft Dataverse, because this is the Dataverse community.
That said, Dataverse software is Free Open Source Software (FOSS) under the Apache 2 license and doesn't cost a dime/quid/buck/cent/...
It's free to install, there are no hidden costs, no license fees etc
If you have a Linux admin around, you should be good to go. There is no hosted offering, so you basically need to pay for all the costs associated with your own hosting. That might involve server housing, storage, computing, but usually the biggest item on the bill are humans taking care of everything.
If you require paid assistance, you can reach out to the GDCC which offers consultancy for installation as well as operation.
You are obviously free to ask question here or on the mailing list. The community is very open and supportive and will try to do their best for free. (Obviously there are limits to the capacity of people doing this voluntarily)
Feel free to add more questions here @saroth :smile: We can always move them to some place else if need be :wink:
@saroth In case you don't know how to get started with an installation - do you know about the extensive documentation? There is an installation guide, too: https://guides.dataverse.org/en/latest/installation/intro.html
One more question, after installation we can customize the code or not? Example, I want to add link, some fields or form, etc.
Can I install it in window?
Windows is not officially supported, sorry. You can try to, but it is highly experimental. We strongly suggest you use Linux.
One more question, after installation we can customize the code or not? Example, I want to add link, some fields or form, etc.
Could you help to reply on this question? This is the last question. Sorry for disturbing you.
It's open source! So of course, you can create a fork and do heavy customizations. Of course forks have drawbacks, too - you need to take care to port your patches to new releases, so you're not left behind on some old version. Usually, we suggest going as far as possible without forking, as it makes maintenance a lot easier.
You can already define your own metadata schemas, so you don't need to fork for this kind of stuff.
Forking really should only be done if there is some feature that you can develop but is not to be included in upstream for some reason. High quality code contributions from the community are always welcome! Feel free to search within existing issues if you miss a feature or create a new issue if no one asked for the same before. Pull request on GitHub should usually be discussed in an issue before you start coding, making sure we can include it in upstream.
Hope that helps! And keep them questions coming! We're here to help each other :smile:
(Also note that a lot of community members are from the Americas and a few hours behind on the clock. I'm in CEST so I was the first to respond :wink: )
Thank you very much for your response
Last updated: Nov 01 2025 at 14:11 UTC