Deploy EdenText
Private, local-first web word processor for .docx and .odt
edentext
Just deployed
Deploy and Host self hosted EdenText (Other) on Railway
This template deploys EdenText, a private browser word processor for .docx and .odt files, as independent community packaging of stffnb/edentext v0.15.0 (AGPL-3.0-only, Copyright 2026 Steffen Becker). It is not affiliated with or endorsed by EdenText, Steffen Becker, Microsoft, or The Document Foundation.
About Hosting EdenText open-source software on Railway (self hosted EdenText template)
EdenText is a browser word processor that opens and saves .docx and .odt files. There is no database, no volume, and no template variables.
Railway pulls the image, serves it over HTTPS, runs a health check on /, and restarts the service if it stops.
Why Deploy EdenText, the self-hosted browser word processor on Railway
Self-hosting EdenText on Railway gives you a private word processor at your own HTTPS URL, and documents stay in the visitor's browser with nothing uploaded in the default template.
Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.
By deploying EdenText on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.
Railway vs Other Hosting Providers and VPS for EdenText self hosting
EdenText is a static browser word processor, so hosting mostly means choosing how much server work you want to manage.
| Provider | What You Get with Railway | What You Get with the Other Provider |
|---|---|---|
| DigitalOcean | A one-click deploy of the unmodified upstream image on port 8080, with a health check on / and restart Always. | A Droplet you provision and run Docker on yourself, with full control of the host. |
| AWS | One public service with no volume and no template variables to set up. | Services such as EC2 where you build the networking, TLS and container runtime yourself. |
| Hetzner | Managed deployment from the template with a single edentext service and HTTPS handled for you. | A low-cost cloud server where you install Docker and keep the container running yourself. |
Keep one replica of the service either way.
Common Use Cases for hosted EdenText
- Drafting a shared thesis chapter: A student opens a .docx from their laptop in the browser, edits it with the ribbon tools, and saves it back to the same file without the text ever being stored on the server.
- Editing a club newsletter: A volunteer uses the Insert and Layout tabs to add columns and pictures to an .odt file, then sends the saved copy to members.
- Reviewing a colleague's draft: A team member opens a .docx received by email, uses the Review tab to track changes, and returns the edited file, keeping the document in their own browser.
- Working on a book manuscript: An author writes in a private browser tab on a domain they control, relying on the References tab for headings and page structure while the document stays on their own device.
- Keeping a private office editor: A small group runs one EdenText URL on their own domain so they can open and save .docx and .odt files without signing up for a hosted document service.
Dependencies for EdenText Docker hosted on Railway
This template deploys one service, edentext, built from ghcr.io/onepush-dev/edentext:v0.15.0. Documents stay in the visitor's browser.
Deployment Dependencies for Managed EdenText Service
The edentext service is public on port 8080, with no volume, no template variables, a health check at /, and restart policy Always. Keep one replica. Documents stay in the visitor browser; nothing is uploaded to the server in the default template.
Implementation Details for EdenText
The image ghcr.io/onepush-dev/edentext:v0.15.0 is the unmodified upstream ghcr.io/stffnb/edentext:v0.15.0 static nginx image, with only the listen port changed from 80 to 8080 on IPv4 and IPv6. The upstream entrypoint still runs and writes edentext.config.json, which is an empty object by default. Optional EDENTEXT_* variables can preset an AI assistant or dictation, or proxy a key at /ai/v1 or /stt/v1; a proxied key is usable by anyone who can open the URL. Those options were not tested on this packaging. When the editor is embedded, the Powered by EdenText attribution and the EdenText logo must stay visible.
How does EdenText compare against other tools
EdenText vs a Desktop Word Processor (Desktop Word Processor Alternative)
- Where it runs: EdenText runs in the browser and needs no installation on the visitor machine, while a desktop word processor is installed application software tied to that computer.
- File handling: EdenText opens and saves .docx and .odt files, and documents stay in the browser. A desktop application keeps files on local disk by default, which suits people who want that without any web hosting.
- Feature depth: Desktop word processors are the more complete choice for heavy layout, add-ins and mature printing workflows. EdenText is a beta project and bugs cannot be ruled out, so keep backups of important files.
EdenText vs a Hosted Document Editor (Hosted Document Editor Alternative)
- Data location: In the default template, EdenText uploads no documents to the server, so the file contents stay with the person editing them. A hosted document editor usually stores files on the provider's servers.
- Collaboration: Hosted document editors are generally stronger for real-time co-editing and sharing links. EdenText is a single-user editor in this template and does not offer that workflow.
- Operation: Hosting EdenText means you run one static web service and keep its address private. A hosted editor needs no servers from you, but you depend on its accounts and availability.
EdenText with Docker vs Railway (Railway Deployment Alternative)
- Setup effort: Running the unmodified upstream image with Docker on your own machine or server needs a Docker host and your own HTTPS setup. Railway deploys the same image as one service with a public domain and no template variables.
- Port and health: The Railway template listens on port 8080 and uses / as the health check with the restart policy set to Always. A plain Docker run uses port 80 unless you map it, and you manage restarts yourself.
- Scaling and state: Keep one replica, since there is no database or volume to share. Docker on a single host offers the same simplicity with more control over networking and cost.
How to use EdenText on Railway?
Follow these steps on your first day after the deploy finishes.
1. Open the public domain that Railway assigned to the edentext service.
2. Choose New document, or open an existing .docx or .odt file from your computer.
3. Edit the document in the browser. Nothing is uploaded or stored on the server.
4. Save the file back the same way, to your own device.
5. If you embed the editor in another page, keep the "Powered by EdenText" attribution and the EdenText logo visible.
6. Keep the service at one replica, and confirm the health check on / is passing.
How to self host EdenText on other VPS Services (EdenText self hosting guide)
EdenText is a static web app, so any server that can serve a folder of files over HTTP will work.
Clone the Repository
Get the source from the upstream project and check out the release you want.
git clone https://github.com/stffnb/edentext.git
cd edentext
git checkout v0.15.0
Install Dependencies
Install Docker on your VPS, the simplest way to run EdenText. Building from source also needs Node.js and npm.
npm install
npm run build
Configure Environment Variables
The default setup needs no environment variables. A proxied API key is usable by anyone who can open your URL, so protect the domain first.
Start the EdenText Application
Run the upstream container, then place your own HTTPS reverse proxy in front of it at your-domain.
docker run -p 8080:80 ghcr.io/stffnb/edentext
Railway handles the HTTPS domain, health check and restart policy for you.
Pricing and License of EdenText (EdenText pricing)
EdenText is AGPL-3.0-only open-source software, so you can self-host it for free under that license.
EdenText hosted vs self hosted comparison (Pricing, features, costs, and more)
This template packages the AGPL-3.0-only software, including the embed-mode attribution term.
Monthly cost of self hosting EdenText on Railway
Railway bills on usage, so the monthly cost depends on the RAM, CPU and services your deployment consumes.
System Requirements for Hosting EdenText on a VPS
EdenText is served as static files by nginx, with no backend.
EdenText is released under AGPL-3.0-only, with an additional attribution term for embed mode. When you embed the editor, the Powered by EdenText text and the EdenText logo must stay visible, legible and unaltered. The upstream author also offers a separate commercial licence; this packaging is the self-host image only, and no licence prices are quoted here. The template asks for no inputs at deploy time, and the default service has no AI or dictation preset. Keep one replica unless you have a clear reason to change it, because local state is not shared across instances.
Frequently Asked Questions (FAQs)
Are my documents uploaded to the server?
No. The default template runs a static editor, and your .docx and .odt files stay in your browser, with nothing saved on the server.
Can I hide the "Powered by EdenText" line when embedding?
No.
Is the AI assistant turned on by default?
No.
Is this affiliated with Microsoft or The Document Foundation?
No.
What should I back up?
Nothing on a volume, because this service has no volume and stores no state.
Template Content
