Groowiki Features
| Feature | Community | Professional | Enterprise | ASP |
|---|---|---|---|---|
| full repository access supporting file, svn and dav protocols |
|
|
|
|
| community support |
|
|
|
|
| professional support1 |
|
|
|
|
| radeox wiki format |
|
|
|
|
| unlimited users |
|
|
|
|
| Java plugin support |
|
|
|
|
| Groovy plugin support |
|
|
|
|
| accessing multiple svn repositories2 |
|
partial | partial |
|
| repository based authentication |
|
|
|
|
| repository based access control |
|
|
|
|
| password file based authentication |
|
|
|
|
| individual plugin access control |
|
|
|
|
| pluggable authentication |
|
|
|
|
1 You can purchase professional support for Groowiki Community Edition. Groowiki Professional, Enterprise and ASP Edition licenses contain one year professional support and new version upgrade.
2 You can configure Professional Edition to use different repository URL for the plugins. Enterprise Edition can be configured to use a different repository URL for each plugin. ASP edition is programmable.
Most of the features of Groowiki are available in the community edition. Community Edition is free of charge and it is open source.
Features of the editions are upward compatible. If a feature is implemented in edition X and X < Y then Y will handle the feature exatly the same way.
Community < Professional < Enterprise < ASP
The codebase of the editions are the same and is available from the download page as Java source.
Features of editions higher than community require license. The license is a Java properties file GPG signed. You get the license file when you purchase an edition.
For futher information on the difference of the editions consult the Users' Guide