• Wikimedia keeps detailed statistics which look like what you want, but I haven't dug too deep so it may be lacking in some way. https://en.wikipedia.org/wiki

• Wikimedia keeps detailed statistics which look like what you want, but I haven't dug too deep so it may be lacking in some way. https://en.wikipedia.org/wiki/Wikipedia:Web_statistics_tool https://en.wikipedia.org/wiki/Wikipedia:Web_statistics_tool https://stats.wikimedia.org/EN/ https://stats.wikimedia.org/EN/ • There is also an API: https://en.wikipedia.org/w/api.php https://en.wikipedia.org/w/api.php You could probably get an estimate of edits per day by requesting versioning metadata (i.e. each version being an edit) on a sample of documents. • I think it will be essential for you to run tests using the actual configuration that you plan to have. Server hardware and the software stack and their respective configurations are a significant factor in the cost of running something like this and are nearly impossible to estimate. There are cases where modifying a single configuration flag can multiply the requests per second you're able to serve. • Additionally, you should probably factor in business-level projections based on the market your project is aimed it - ask yourself: will your project be as popular as wikipedia? Will your users have the same ratio of pure consumers to editors as wikipedia? Consider identifying user characteristics in your market segments which correlate with whether someone is a pure consumer vs. an editor.