FAQ

A wiki: a website where your team writes, organizes and finds its knowledge together, which you run on your own computer or server instead of renting from someone else. See What is Tesria.

Yes. Tesria is open source under the Apache License 2.0: you may use it, change it and run it for anything, including commercially, with no fee and no limit on people or pages. See License and credits.

No. Writing and organizing pages is all done in the browser. Installing it needs someone comfortable typing a few commands into a terminal, once; Quick start has every one of them.

There is nothing to install: Tesria works in the phone’s own browser, reading and writing, with menus made for touch. See Tesria on phones and tablets.

A computer or server that runs Docker, with at least 2 processor cores, 2 GB of memory and 20 GB of disk. An old laptop or a small home server is enough to start. See System requirements.

No to both. Tesria runs happily on a home or office network with no domain and no internet connection, reached by the server’s name, such as studio.local. A domain is only needed if people will open it from outside your network. See Opening Tesria by name.

On your own network, Tesria makes its own certificate, which each device has to be told to trust, once. It takes about three minutes: see Trusting the local certificate.

Two commands, with a backup first. See Upgrading.

Yes, from the moment Tesria first starts, with nothing to set up: daily copies of everything, and a continuous record of changes that can bring the wiki back to any moment. Those copies are on the same machine, though, so also set up an offsite copy. See Backups and recovery.

With an offsite copy, you install Tesria on another machine and restore from it. See When the machine is gone. Without one, the backups are lost with the server, which is why an offsite copy matters.

On your server, in Docker’s storage: the database, the attached files and the backups each have their own. Nothing is stored anywhere else.

Only what you set up: email through your mail server, offsite backups to the place you choose, and webhooks to the addresses you enter. When someone pastes a link that shows a preview, your server fetches that page’s title and picture. A server on a real domain also asks Let’s Encrypt for its certificate. Nothing is sent to the people who make Tesria.

Any page downloads as Markdown, HTML or PDF, and a whole space as a website or a wiki pack. Scripts can read everything through the REST API. See Exporting and publishing.

Not directly. Tesria imports its own wiki packs, so a space can move from one Tesria to another; and a script can create pages through the REST API, or an AI assistant through MCP.

Yes: export it as a wiki pack, with its history, comments and files, and import the pack on the other one. See Wiki packs.

Yes. A new space is open to everyone signed in, and you can limit any space to particular people or groups, and any page further still. See Who can see a space and Restrictions.

Yes, for spaces you choose to publish, such as public documentation. It takes two switches, one for the whole wiki and one for the space, so nothing is public by accident. See Public reading.

Yes, when live editing is set up: everyone sees each other’s changes as they type. See Editing at the same time.

Yes, through MCP, with a token you make. An assistant sees and changes only what you can, can be kept to reading only, and what it writes shows up in the page’s history. See MCP.

Choose Forgot your password? on the sign-in page, or ask an administrator for a reset link. See Resetting a password.