GROWI Team Wiki on AWS - Managed Support

AWS Applications

GROWI, an open source team wiki and knowledge base with Markdown pages, real time collaborative editing and a navigable page tree.

Base
Hardened build
minimal ports, security patches applied at build time
Access
Unique credentials
generated on first boot, readable only by root
Verified
Boots working
services pass a health gate before release
Support
24/7, 365 days
by email and live chat, 24 hour response SLA

Overview

GROWI is an open source team wiki and knowledge base built for organisations that want to capture and share what they know. Pages are written in Markdown with live preview, diagrams and math, and edited collaboratively in real time so several people can work on the same page at once. Content is organised as a hierarchical page tree with links, tags, comments and a full revision history, making it easy to browse, cross reference and keep documentation current. It runs as a self contained Node.js application backed by MongoDB, so a single instance holds your whole knowledge base, and full text search can be added later by attaching OpenSearch or Elasticsearch when you outgrow the built in browsing.

Why the cloudimg image

The cloudimg image is hardened and fully patched with GROWI built from the pinned upstream release, MongoDB and an nginx reverse proxy already wired together, so the wiki is serving with no setup wizard left exposed. A unique administrator password, MongoDB password and password hashing seed are generated on every first boot and stored in a root only file, and self registration is locked closed so the wiki is never world writable. Page content and attachments sit on a dedicated resizable data volume separate from the application tier, and every instance is backed by 24/7 cloudimg support.

Common uses

  • Team knowledge base
  • Engineering runbooks
  • Collaborative documentation

Key features

  • Production ready GROWI 7.5 built from the pinned upstream release on bare metal Node.js 24 with MongoDB 8.0 and an nginx reverse proxy - no containers, no manual installation, no setup wizard. Real time collaborative Markdown editing, a hierarchical page tree, revision history, comments and tags are all working the moment the instance boots.
  • Secure by default with zero shared credentials: every instance generates its own administrator password, MongoDB password and password hashing seed on first boot, stored in a root only file. Self registration is locked closed so a public wiki is never world writable, MongoDB runs with authorization enabled bound to loopback, and no two deployments ever share authentication material.
  • 24/7 technical support from cloudimg engineers by email and live chat with a one hour average response for critical issues. Support covers deployment and sizing, MongoDB administration and backup, TLS termination, attaching OpenSearch for full text search, GROWI upgrades and performance tuning - so your team focuses on writing, not on running the wiki.

See it running

Real screenshots taken while testing this image against its deployment guide.

GROWI Team Wiki on AWS - Managed Support screenshot 1 GROWI Team Wiki on AWS - Managed Support screenshot 2 GROWI Team Wiki on AWS - Managed Support screenshot 3 GROWI Team Wiki on AWS - Managed Support screenshot 4

Description

This is a repackaged open source software product wherein additional charges apply for cloudimg support services.

## A Team Wiki Your Organisation Actually Owns

GROWI is an open source team wiki and knowledge base built for organisations that want to capture and share what they know. This image delivers GROWI 7.5 fully built and configured on a bare metal Node.js and MongoDB stack, with no containers to manage, so your team can create its first page within minutes of launch.

## Who This Is For

Engineering teams consolidating runbooks, architecture decisions and onboarding material into one navigable page tree with full revision history. Product and operations teams drafting specifications together in real time, where several people editing the same page simultaneously is the normal way of working. IT administrators who need a self hosted wiki inside their own VPC without spending ops cycles on installation, credential rotation or reverse proxy configuration.

## What Makes GROWI Different

  • Real time collaborative editing so multiple authors work on one page at once without locking or merge conflicts
  • Markdown first authoring with live preview, diagrams, tables and math notation
  • Hierarchical page tree where pages nest under paths, making a large knowledge base navigable rather than a flat list
  • Revision history, comments, tags and page links across the whole wiki
  • Attachments stored in the database so page content and its files stay together on one data volume

## Application Stack

  • GROWI 7.5 built from the pinned upstream release on Node.js 24
  • nginx reverse proxy on port 80, WebSocket aware for real time collaboration, with an unauthenticated health endpoint for load balancer probes
  • MongoDB 8.0 datastore with authorization enabled, bound to the loopback interface
  • Reach the wiki through nginx on port 80; the application port 3000 needs no inbound rule and should be left closed in your security group

## Secure By Default

Unlike images that ship a shared or documented password, this one generates every secret on each first boot:

  • A one shot service completes the GROWI installation automatically, with no browser setup wizard left exposed for the first visitor to claim
  • An administrator account is created with a per instance password written to a root only file
  • A fresh MongoDB password and password hashing seed are generated and applied
  • Self registration is locked closed, so the wiki is never world writable on a public address
  • No shared credentials exist anywhere in the image

## Storage Layout

Two dedicated EBS volumes ship with the image, separate from the operating system disk and each independently resizable: the MongoDB datadir holding pages, revisions and attachments, and the GROWI application tier. Both are mounted by filesystem UUID.

## Getting Started

1. Launch the image on an m5.large instance or larger, with ports 80 and 443 open in your security group

2. Connect over SSH and read the generated administrator password from the root only credentials file

3. Browse to the instance address and sign in as the administrator

4. Create your first page in the Markdown editor and organise content into a page tree

5. Invite your team from the admin area, where user management, access control and appearance are configured

6. Attach OpenSearch or Elasticsearch later if you want full text search across a very large wiki

## Recommended Instance Sizing

  • Minimum: m5.large (2 vCPU, 8 GB RAM) for small teams
  • Recommended: m5.xlarge (4 vCPU, 16 GB RAM) for teams above 50 concurrent authors
  • Storage: grow the database volume as your wiki and attachments grow
  • Networking: ports 80 and 443 for browsers, port 22 for administration

## 24/7 cloudimg Support

Every deployment is backed by cloudimg engineers available around the clock by email and live chat. Support covers:

  • Deployment guidance and instance sizing
  • MongoDB administration, backup and restore
  • nginx reverse proxy and TLS termination with Let's Encrypt or your own certificates
  • Attaching OpenSearch or Elasticsearch for full text search
  • GROWI upgrades and migration assistance
  • Performance tuning and troubleshooting

Critical issues receive a one hour average response time.

## Evaluation

Launch an instance to evaluate GROWI with your team and terminate at any time with no long term commitment.

GROWI is a trademark of its respective owner. All product and company names are trademarks or registered trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.

Related technologies

team wikiknowledge baseinternal documentationmarkdown wikiself hosted wikicollaborative editingengineering runbooksintranetdocumentation platformcontent collaboration