Wiki.js Hosting

On a new installation, the upstream setup screen asks for the administrator’s email address, a password and the full URL of the wiki. Use your pod’s HTTPS address, finish installation, then sign in with the account you created. Start with a home page and review access settings before adding private content. The Wiki.js 2.x setup guide shows this application setup screen; its server-provisioning instructions are not needed for a pod.

No. PikaPods sets up and runs Wiki.js for you, including OS and app updates and HTTPS. You won't touch Docker or a server. Your files and database stay accessible if you ever want to move them elsewhere.

Review the Guests group first: to require login for every page, remove its read access using the private-wiki instructions. Create groups with both the required global permissions and matching page rules. Local authentication is built in; optional authentication modules support services such as Google, GitHub, LDAP and OpenID Connect. External providers need their own configuration, and enabling self-registration is separate from granting access to pages.

No. The database stores the live content, so external storage is optional. If you enable Git synchronization, use a repository dedicated to Wiki.js and configure authentication and the sync schedule; changes are not necessarily pushed immediately after each save. Other storage targets have their own capabilities and account requirements. Any charges from your chosen repository, storage or identity provider are separate. See the storage overview and Git guide.

Set up incremental backups to S3 in your pod settings for automatic nightly snapshots, or download your files and database yourself. We keep whole-server backups for server failures, but they aren't a per-pod restore service, so your own backup is what protects your data.

You can use Wiki.js instead of Confluence and GitBook. PikaPods runs it for you, and you can move your files and database elsewhere.

Both organize team pages with permissions and search. Confluence is a hosted workspace connected to other Atlassian tools. Wiki.js offers Markdown and visual editors, path-based access rules and optional Git sync, on your own pod. It has fewer built-in collaboration features, so check commenting and live editing if your team relies on them.

The documented wiki workflow is through a web browser connected to your server, rather than a desktop or mobile sync app. Git storage can exchange page files with an external repository so you can edit them in other tools, but it is not a browser-offline mode or a guarantee that every wiki feature round-trips through those files.

No. You add prepaid credit and your pods are billed by the hour from that balance, rounded up to full hours. There are no contracts or minimum terms: delete a pod anytime and billing stops. Optional automatic top-ups keep your pods running without manual payments.

You do. And you're in full control. If you ever want to download, migrate, edit or delete your data, just enable file and database access for your pod and it will be right there.

Yes. Wiki.js is part of our Green Heart program, so part of the revenue from every deployed pod goes to the project.