Service description

Version 10.0 · Last updated: 23 October 2026
Describes WebDonkey 1.0.41, WebDonkey Editor 1.0.53 and WebDonkey Pages 0.1.6.

1. Scope

This service description sets out what our products do. It forms part of the contracts you conclude with BuI Hinsche GmbH via our online shop at shop.webdonkey.io (§ 2(5) of our Terms). The version valid at the time of your order applies; we send it to you as a PDF with the order confirmation and the confirmation of payment. The product and feature pages on webdonkey.io and in the shop and the documentation in the apps explain the functions in more detail; this service description governs the scope owed.

We develop the apps further. New versions may add functions; changes affecting existing functions are governed by § 9(5) of the Terms. Functions that we later move into the Free scope remain included in the paid packages. The current prices are shown in the shop on the page of each product, in the basket and in the order summary; the “Payment and shipping” page explains how they are made up.

2. For all apps

• Local on your Mac. WebDonkey, WebDonkey Editor and WebDonkey Pages run on your Mac. The apps need no servers of ours to function, and we store none of your project data. The apps talk to our server only for licence, updates, release notes, online documentation and theme gallery (privacy policy, section 9).
• System requirements. A Mac with macOS 11 or later, with Apple chip or Intel processor (one app for both), and an internet connection for download, updates and licence verification. Further requirements are listed for each app.
• Download and updates. You download the apps free of charge with your customer account from the download page, at most ten downloads per customer account and day. Updates are included in the Free scope and, during the term of a subscription, at no additional cost. Each app checks the signature of an update before installing it. Updates required to keep the apps in conformity with the contract, including security updates, are provided at least for the term of your subscription. The statutory warranty rights for digital products apply to defects (§§ 327 et seq. German Civil Code).
• Free scope. All three apps can be used permanently free of charge without a licence, within the scope of sections 4.2, 5.2 and 7.2.
• Not open source. The apps are not open-source software. The apps show the licences of the open-source components they contain.
• Third-party software. What the apps install at your request (such as PHP, databases, web servers, coding agents) they load from the manufacturers' sources; this software is not the subject of our contract.

3. Licence, devices and packages

• Licence key. Each subscription provides a licence with a licence key. You find it in your customer account under “WebDonkey licenses” and enter it in the app.
• One device at a time. A licence applies on one device at a time (one seat). WebDonkey, WebDonkey Editor and WebDonkey Pages on the same Mac, with the same user and the same licence, together take one seat. You may install the apps on several of your own Macs. When it is quit, the app releases the seat; if the device does not report in for a longer period, the next device to make a request takes the seat. You can sign devices out in your customer account. Simultaneous use by several people requires a separate licence for each person.
• Check and offline use. The apps check the licence at start and then every ten minutes. Without a connection, the licence's functions remain usable until the end of the billing period confirmed at the last check plus three days.
• Seats. If you order a product several times, the licences (seats) run in one subscription; each seat can be cancelled individually.
• Coupling. In your customer account you couple a Pages licence to a WebDonkey licence; one key then carries both. Each coupled licence remains a contract of its own. We never couple Pages licences automatically.
• Add-ons. SEO package, maintenance package, maintenance add-on and Pages add-on only take effect while they are assigned to a running licence they require (table in section 8). At most one SEO package and at most one maintenance package can be assigned and at most one Pages licence coupled per licence, any number of add-ons. We assign an SEO package, a maintenance package or a maintenance add-on automatically where it is clear which licence it belongs to; you assign a Pages add-on to a Pages plan yourself in your customer account. You can change couplings and assignments up to three times per licence within 30 days. If the carrier of an add-on (the licence or plan it requires) ends regularly, for example after a cancellation, and the add-on runs longer, it becomes a licence of its own with a new key; it unlocks nothing until you assign it to a matching licence, and it continues until you cancel it. If the carrier ends through withdrawal, full refund, chargeback or termination for good cause, the add-on ends with it; if you as a consumer withdraw from the contract for the carrier, you are no longer bound by the add-on either and get its payments back, even if you bought it in a different order. You can untick such an add-on when you withdraw using the “Withdraw from contract” form; it then continues as a licence of its own with a new key, and we do not refund its payments (Terms § 5(8), § 360 of the German Civil Code).
• Company accounts. A company account can invite team members and share individual licences with them; the team member sees the key and uses it in the apps. The company account remains the contracting party.
• Without an active licence. If a licence ends or is not active, the apps run in the Free scope. No data is deleted (Terms § 7).

4. WebDonkey

4.1 What WebDonkey is

WebDonkey sets up and manages local web development environments on your Mac: sites with their own domain and HTTPS, the services they need such as web servers, PHP, Node.js and databases, plus tools for mail, logs, monitoring, scheduled tasks, virtual machines, terminal, API requests, workflows, local AI and the management of Claude Code and MCP servers.

4.2 Free scope

Without a licence you use WebDonkey with these functions and limits:

• any number of local sites with their own domain, of which at most three with HTTPS at the same time;
• services in several versions side by side, at most six services started at the same time (the front proxy does not count);
• editing the configuration files of the services, except the shared php.ini for all PHP versions;
• creating and managing databases; Adminer, Mailpit and log files open in the browser or externally;
• website monitoring: one project with three targets, with the full range of functions;
• scheduled tasks: three;
• virtual machines, certificates, terminal tools (aliases, SSH keys, SSH hosts), toolbox, local AI chat;
• own prompt designs for the terminal: three;
• API client: sending and testing requests, without saving;
• workflows: three, each with the last 20 runs, built from the building blocks of the Free scope;
• toolbox collections: one colour palette, 20 icon favourites, five sandbox snippets, ten remembered components, one own component source, five animations;
• managing subscriptions: six;
• Claude Code: view instances, limits and configuration; view, check, stop and remove MCP servers of all clients, add two yourself;
• fetching projects from the server via SSH and adding them as a made-safe local copy (“fetch locally”, section 6.3);
• the two built-in themes and themes from the gallery; documentation; settings.

Monitoring (also with Premium): WebDonkey checks the targets at the intervals set while it is running on your Mac. While your Mac has no internet connection or is asleep, WebDonkey neither checks nor notifies. It reports an outage when a target is unreachable in two check rounds in a row, and “reachable again” only after a reported outage; it combines the outages of one check round in one notification, and likewise the targets that are reachable again. An outage that already exists when WebDonkey starts only shows in the app. If a target answers with Shopware's maintenance page, WebDonkey shows the status “maintenance” and reports neither its start nor its end; other error responses count as an outage. Before a certificate or a domain expires, WebDonkey notifies you several times, last on expiry; for domains, as far as the directory service states an expiry date.

4.3 WebDonkey Premium

WebDonkey Premium removes the limits of section 4.2 (workflows with up to 200 runs in the history) and also unlocks:

• Mailpit, Adminer and log files embedded in the window, adding your own log files and following them live;
• editing the shared php.ini for all PHP versions;
• backups: backup sets per project with schedule and restore, plus the backup of the app itself;
• site packages (framework scaffolds when creating a site);
• remote: SSH and SFTP connections to your servers with terminal and file manager, databases, backups, cron jobs and logs on your servers and mailboxes of your domains: reading mail (the mailbox on the server read only) and sending your own mail through the account's outgoing server (SMTP), with Cc, Bcc, text or HTML and up to 20 attachments of at most 25 MB together, as a test also only to Mailpit; sent and failed mails stand with their result in the outbox on your Mac (of attachments only name and size), and WebDonkey files no copy in the mailbox's “Sent” folder;
• making the local copy runnable when fetching locally (section 6.3);
• notes and Second Brain: creating or adding folders of notes (also existing Obsidian vaults) and setting them up as a brain of one of three kinds, which you choose when doing so (WebDonkey suggests a fitting one) and can change later without anything changing in the folder: Claudian brain (Claude works as in the Obsidian plugin Claudian, see below), WebDonkey brain (a CLAUDE.md that tells Claude how to keep and read the brain in a fixed structure) or personal Second Brain (see below); an existing CLAUDE.md stays unchanged by the choice. Folders for which you have not chosen a kind (also brains from earlier versions) are assigned by WebDonkey according to their content, Obsidian vaults usually as a Claudian brain. “Let Claude set it up from these notes” (Claudian and WebDonkey brain) starts Claude Code with a guide under which Claude looks at the notes, proposes a guide for working with Claudian or folders, types and connections, and changes something only after your yes; how Claude follows the guide is up to Claude. On request WebDonkey first creates a zip backup of the folder next to it. An overview per brain whose graph you filter by folders and tags and which shows the brain's kind; assigning brains to Claude projects; opening a brain in Obsidian if Obsidian is installed;
• personal Second Brain: WebDonkey puts a setup guide into the folder as CLAUDE.md. “Start setup with Claude” starts Claude Code in the brain; following this guide, Claude asks you in a conversation about your profile, your projects, areas and topics and, once you agree to the proposed structure, creates folders, context notes and the brain's own rules (a new CLAUDE.md). What comes out depends on the conversation; WebDonkey provides the guide but owes no particular result from Claude. The guide provides for the Obsidian Skills (section 4.4);
• Claudian brain: “With Claude”, starting Claude and resuming a chat start Claude Code in the brain the way the Obsidian plugin Claudian starts it (following its version 2.3.27): with Claudian's system prompt and the folder's Claudian settings (model, effort, permission mode, environment variables, custom instructions, skills and the folder's MCP servers, the latter without asking), and without such settings with Claudian's defaults; the overview shows what Claude starts with. In the permission mode “automatic” (Claudian's default, Claude Code's auto mode) Claude Code checks many commands and file changes itself instead of asking you, in the mode “no questions (YOLO)” it does not ask at all (§ 11(6) of the Terms). Claude Code's question whether you trust the folder does not come up: like Claudian, WebDonkey treats the folder as trusted for this session; so choose this kind only for folders whose content you trust. Chats from Claudian appear with their titles in the list of sessions and can be resumed; WebDonkey enters a chat begun in WebDonkey into Claudian's history if Claudian is set up in the folder. Such a session does not get the brain MCP;
• with Claude: “With Claude” starts Claude in the brain and gives every message the open note and the selected text. “Edit with Claude” rewrites the selected text or the paragraph at the cursor according to your instruction, on your click or with ⌘⇧E, in Live Preview, when editing and from the preview, through your Claude Code with Claudian's instructions (in a Claudian brain with its model and settings); Claude may only read (files of the vault, web search, fetching web pages) and can ask back; WebDonkey applies the change only when you accept it;
• display as in Obsidian: the notes page shows notes the way Obsidian's reading view does: the title above the note (inline title, according to the vault's setting), properties by their type, wikilinks with alias, heading and block (jumping there), Markdown links, unresolved links paler (a click creates the note), embeds of notes, sections, blocks, images (with size), PDF (with page), audio, video, canvas and bases, callouts (also foldable), highlights, comments, tasks, footnotes, formulas (KaTeX), Mermaid diagrams, HTML (sanitised), coloured code, tags (nested ones too; a click searches the notes with the tag), embedded searches (query blocks) with their hits per file, and backlinks; typing “[[” suggests links including aliases. Bases appear with their views as a table, cards or a list. Images that a note embeds by a web address are loaded, as in Obsidian, directly from the server concerned when shown (privacy policy section 10.6); without an internet connection they are missing. Per vault you can switch off “Load content from the web” (default: on); a placeholder then takes their place, and only a click loads the individual image. The note tree also shows attachments, canvas and base files in Obsidian's order; canvas files appear as a board with cards, groups and connections. Renaming and moving notes, attachments and folders on the notes page updates all links to them, in text, properties and canvas cards, each in its own form; properties stay unchanged when saving;
• editing as in Obsidian: notes open in Live Preview (formatted while you write, Markdown only at the cursor) unless the vault has switched it off in Obsidian; next to it Edit (Markdown), Split and Preview. In addition an editor for properties, the inline title renames the note, “[[” suggests notes including aliases, headings and blocks, keyboard shortcuts as in Obsidian, and WebDonkey stores pasted or dropped files in the vault's attachment folder. Editing bases: views, sorting, groups, filters, properties and columns, formulas and column width; cells write into the note's properties, “New” creates a note. Editing canvases: cards, groups, connections, colours and text, with undo. Everything is saved in Obsidian's format;
• personal Second Brain after its setup: when WebDonkey starts Claude there, it gives Claude a working guide under which Claude works like an assistant inside Obsidian: following the vault's CLAUDE.md, if there is one, in Obsidian Markdown and according to the vault's settings (link format, folders for attachments, daily notes and templates), without adding WebDonkey-brain fields and without changing .obsidian/ unasked; how Claude follows the guide is up to Claude. In brains without the rules of a WebDonkey brain the brain check only checks whether links find their target;
• structure of a brain: the notes and folders as a mind map with named connections (kind, target and reason are stored in the note's frontmatter), filters by connection kind, status, product and tag, a search by name, alias, folder and #tag that highlights the hits on the map and shows a chosen hit, creating, changing and deleting connections, new notes from the template of their type, renaming with the links updated, the brain check against the brain's rules, a scaffold from the code (for pages, commands, services and data that WebDonkey recognises in a project folder you choose, it creates the missing notes; the project folder is only read, existing notes are never overwritten) and an AI guide to copy that describes how the brain is structured and read;
• brain MCP: if you start Claude in a WebDonkey brain or a personal Second Brain, the session gets an MCP server on your Mac with five tools that only read (search, note with its connections, click path, consequences of a change, brain check); your MCP configuration stays unchanged;
• API client: saving requests, collections, environments and history;
• local AI: specialists with fixed context and coding agents against your local model;
• own themes with the theme editor and submitting them to the theme gallery;
• Claude Code: editing hooks, agents, MCP servers, plugins, settings and CLAUDE.md, usage by day, project, Second Brain and model, searching and resuming earlier sessions;
• workflows in full: app events and file changes as triggers, a memory between runs, own code, mail, database queries, controlling sites and services, commands on your servers and the local AI;
• MCP: adding any number of servers, also to several clients at once, editing, switching on and off, copying, own clients, full tool lists and logs;
• the Premium functions of WebDonkey Editor (section 5.3).

The overview, the structure and the brain MCP take into account at most 5,000 notes per brain, at most 1 MB per note and at most 128 MB in total; for larger brains they show a part.

Limits of the display and editing as in Obsidian: WebDonkey does not run Obsidian plugins; their blocks (such as Dataview queries) appear as code. In Live Preview you edit tables and callouts as Markdown with a click, without an editor of their own for cells. Canvas files embedded in a note stay a view; the canvas file itself can be edited. Claudian brains follow Claudian when starting Claude; WebDonkey does not reproduce Claudian's own chat window (such as file checkpoints and generated titles), Claude runs in the terminal. From the web the view only loads images: web page cards of a canvas show their address, and a click opens it in the browser; it does not embed audio, video or web pages from the web. HTML in notes appears sanitised, without scripts.

The SEO package, the maintenance package and the plans of WebDonkey Pages are not included.

4.4 Requirements

In addition to section 2: to install services, WebDonkey accesses the manufacturers' sources. Managing Claude Code requires an installed Claude Code, local AI a local model that WebDonkey loads at your request. Notes and Second Brain do not need Obsidian; “Open in Obsidian” requires an installed Obsidian. Setting up a personal Second Brain, “With Claude”, “Edit with Claude” and “Let Claude set it up from these notes” require an installed Claude Code; a Claudian brain does not need the Claudian plugin, and WebDonkey uses its settings if they are in the folder. The guide provides for the Obsidian Skills, a freely available offer of a third party (github.com/kepano/obsidian-skills, MIT licence). The guide instructs Claude to ask you before installing them and to continue without them only if you expressly wish so. WebDonkey itself does not download the skills.

5. WebDonkey Editor

5.1 What the Editor is

WebDonkey Editor is a code editor for macOS. It runs on its own or together with WebDonkey. With WebDonkey it shows your sites and services, and you choose in the Editor, per project, the PHP and Node version that terminals and Claude sessions in the project folder use; for a site, its version from WebDonkey applies, even while WebDonkey is not running. A WebDonkey Premium licence unlocks the Premium functions of both apps; the Editor also checks it itself if WebDonkey is not installed.

5.2 Free scope

Editing code with tabs and split views, search and command palette, project tree with subprojects (a folder of the project shown, via right-click, as an extra collapsible section below the project; the same folder, no copy, can be renamed and removed again, one level, only within the window's folders), Git with changes in the margin and Git graph, terminal, search across the whole project, problems and TODOs, starters for scripts, viewing images, PDF, Word and Excel files (editing and saving images, PDFs, Word and Excel files too), Claude Code in the terminal and Mission Control, local AI (with Ollama also downloading and deleting models and setting the context window through a memory budget), viewing MCP servers, checking them simply and adding two yourself, local databases (also your own connections to MySQL, MariaDB and PostgreSQL servers on your Mac, for example from Homebrew, DBngin or Postgres.app), mail from Mailpit (opened in the browser), widgets, the built-in themes and your own themes, viewing the theme gallery, updates and documentation.

In Mission Control this includes:

• Claude Code's command list when you type “/” in the message field, for sessions in a terminal of the Editor, not in Claude Code's full-screen display;
• going on after a usage limit: if Claude Code does not continue by itself, Mission Control continues the session once your quota is available again, as long as the Editor is running; you can stop the waiting for each session;
• continuing after an update: Claude sessions interrupted by an update of the Editor go on after the restart (from the first update after version 1.0.44);
• scheduled tasks that Claude Code creates in a session: the chat shows them as an entry of their own with the schedule in words, whether once, recurring or durable, and the prompt, plus the next run and the job ID where Claude Code reports them;
• the session list by the projects open and recently opened in the Editor. Each folder of a project window (the project and the attached folders of a combination) and each subproject counts as a project of its own. The picker above the list offers “All projects”, an entry for each open project (the folders of a combination under its name, a subproject under its project) and below them, under “Recent projects”, the recently opened projects (the first ten, as in the menu); each entry shows only that project's sessions. Under “All projects” the sessions of the open projects come first, then those of the recently opened ones, each grouped by project (the folders of a combination indented under its name, a subproject under its project), and last, under “Not assigned”, the sessions that belong to none of these projects, for example ones started in another folder;
• in the “New session” dialog the field “Project” with “No project”, one of the open or one of the recently opened projects (also a single folder of a combination or a subproject), without opening it: it fills in the start folder, which you can change freely; the session belongs to the chosen project even with a different start folder. Without a chosen project, a session belongs to the project in whose folder it starts, a subproject before its project;
• the switch “Skip permission prompts” (off at first, with a warning when you first turn it on): Mission Control then starts Claude in Claude Code's mode “bypassPermissions”, and Claude runs commands and file changes without asking. If Claude Code's settings forbid this mode, the switch is locked.

5.3 With WebDonkey Premium

• Servers via SSH and SFTP: opening and saving files on the server, synchronising folders, SSH terminal and search on the server;
• databases on your servers and mailboxes of your domains (read only);
• Mailpit in the Editor;
• notes and Second Brain next to the code, in the sidebar or as a tab: creating or adding folders of notes (also existing Obsidian vaults), choosing the notes folder in the Editor yourself (the active one from WebDonkey is only the default), setting them up as a brain of the kinds of section 4.3 (Claudian brain, WebDonkey brain or personal Second Brain), also “Let Claude set it up from these notes”, an overview per brain with its kind, starting Claude in a brain (every session started this way gets the brain assigned; in a Claudian brain Claude starts as described in section 4.3), opening a brain in Obsidian if Obsidian is installed; open tasks in the widget;
• for a personal Second Brain “Start setup with Claude”: a new session in Mission Control with the brain as start folder and assigned Second Brain, in which Claude runs the setup as described in section 4.3;
• editing notes in Live Preview as in WebDonkey (section 4.3, “editing as in Obsidian”) or as Markdown in the code editor, “Edit with Claude” as in WebDonkey; the preview of a note with the display of WebDonkey's notes page (section 4.3, “display as in Obsidian”, with the same limits, also for images from the web, with the same setting “Load content from the web” per vault); typing “[[” in the code editor makes the Editor suggest the vault's notes and files including aliases (without headings and blocks); a click on a tag lists the notes with this tag above the note tree. The note tree also shows attachments, canvas and base files; images and PDF open in the viewer, canvas and bases for viewing and editing as in WebDonkey (“Open as text” shows the file as text). Renaming in the note tree, folders too, updates the links to it as in WebDonkey. In a personal Second Brain after its setup Claude works as described in section 4.3; the preview only writes what you click (such as creating a linked note that does not exist yet);
• the structure of a brain in the notes tool as in WebDonkey (section 4.3: mind map, search, editing connections, templates, brain check, scaffold from the code, copying the AI guide); structure and overview are in the sidebar, and “Open as tab” opens them as a tab; a note opens in the Editor with a click;
• local AI: suggestions while typing and coding agents against your local model, started in the project folder with one click;
• Claude Code: editing agents and hooks, session list, starting Claude directly in Mission Control;
• Mission Control in a Claudian brain as in Claudian: the open note and selected lines go to Claude with the message, “@” suggests notes and folders of the brain, [[wikilinks]] in answers open the note, chats from Claudian appear with their titles in the session list and can be resumed, and the Editor enters new chats into Claudian's history; Claude Code's trust question does not come up there, as in WebDonkey;
• creating, changing and removing Claude projects in Mission Control and starting new sessions with their defaults (Claude access, Second Brain, model, effort); a project open or recently opened in the Editor whose folder belongs to a Claude project (also as a subfolder) starts new sessions with that project's defaults; assigning a notes folder to a project or a session as its Second Brain; sessions with a Second Brain carry a mark with the brain's name in the session list, and Claude sessions in Mission Control with an assigned Second Brain get the brain MCP (section 4.3);
• using colour presets, taking over presets from the theme gallery or pasting them as code, and sharing your own presets and submitting them to the gallery;
• managing MCP servers as in WebDonkey (section 4.3).

5.4 Requirements

In addition to section 2: functions around sites, services and local AI need WebDonkey on the same Mac in the current version (local AI without WebDonkey an Ollama you start yourself); database functions the command-line client mysql or psql; Claude functions an installed Claude Code; “Open in Obsidian” an installed Obsidian. For setting up a personal Second Brain, section 4.4 applies.

6. Add-ons to WebDonkey Premium

6.1 SEO package

Requirement: a running WebDonkey Premium licence to which the SEO package is assigned. Premium is not included. Can be ordered with personal and company accounts, monthly.

Functions:

• SEO audit: a crawl across the whole website, a section or a list of addresses, with adjustable scope, click depth, speed, robots.txt, parameters and exclusions, also for password-protected pages (basic auth); findings by content, SEO and technology with the affected pages, scores and history compared with earlier runs; pages on hosts other than the start domain (such as subdomains) are shown with their host and can be sorted by host; audits can be deleted from the history together with all data they created on your Mac;
• website check (security headers, redirects, robots.txt and sitemap, server response time, access for AI crawlers, mail records of the domain), check of resources, page inspector and checking a single address;
• accessibility check according to WCAG 2.2 (level AA, optionally A or AAA) with axe-core and our own checks, with comparison images for the findings;
• reports as PDF (optionally with your company name, logo and a contact line; single audits can be left out of the PDF's history and comparison, and its appendix names them), the page table as CSV and the whole report as JSON.

Limits: The accessibility check is an automated check; it does not replace a full audit under BITV 2.0 or EN 301 549. We do not owe any particular ranking in search engines.

Requirements: For accessibility, a Chromium browser installed on the Mac such as Google Chrome, and Node.js (via WebDonkey's services page); WebDonkey loads the test module from the npm registry the first time.

End: When the SEO package ends or is not assigned to a running WebDonkey Premium licence, its functions are locked; the monitoring of the Free scope remains. If the WebDonkey Premium licence ends, section 3 applies to the SEO package.

6.2 Maintenance package

What it is: An add-on to WebDonkey Premium, for company accounts only. It unlocks functions in WebDonkey with which you look after websites on servers. The software runs on your Mac. We do not maintain any websites ourselves, do not access your servers and receive no data from your websites. The package is made for working on live websites. There, WebDonkey changes only what you start, and only after you have confirmed the plan of the changes; it creates a backup first, when restoring a backup only if you do not deselect this.

Tiers: 10, 30 or 100 active maintained websites, plus maintenance add-ons with 10 more websites each, monthly or annually. For more than 150 websites we make an individual offer on request.

Quota: Active maintained websites count; a website is one live target, its staging and local copies do not count separately. Archiving frees the place; reports and history remain readable. If the quota drops, the oldest websites stay active and the most recently added ones are locked; nothing is deleted.

Functions:

• adding maintained websites per server connection; WebDonkey detects system and version;
• staging on the same server, built from live and refreshable, with replaced personal data, without sending mail or running scheduled tasks, protected by access protection or the system's maintenance mode;
• local test copy of a maintained website as a site with a .test address on your Mac, with replaced personal data;
• pushing changes: comparing fields between staging, local copy and live and pushing them one by one; conflicts with changes on live are shown; deletions are shown but not pushed;
• transferring files for simple websites without a system, with a plan, a backup of every file and undo of the last transfer;
• pushing extensions (plugins, themes, modules) from staging or a local copy;
• undo: pushed content can be written back per push as long as the fields on live have not changed since;
• a backup before every write on the server, optionally also on the Mac; at least the last ten per environment of a website (live, staging) are kept on the server and on the Mac, unless you delete some yourself. You can delete backups in the website's “Backups” tab, under Remote › Backups and in the storage space notice, except the backup of the latest push and that of an open Shopware update; WebDonkey also removes the file on the server or the Mac (if that fails, the backup stays with a notice);
• restoring a backup: the database, the folders or both go back into the environment and folder the backup comes from. You choose whether the folders are merged (files from the backup overwrite the existing ones, added ones stay) or replaced (files added since the backup disappear); for backups taken before updates and extensions WebDonkey suggests replacing. You choose whether WebDonkey first saves the current state as a backup of its own (default: on); without it there is no backup of the state before the restore. For Shopware 6 WebDonkey then clears the cache, compiles the themes and installs the assets, and shows what of this did not succeed;
• updates: overview of core, extensions and packages (Composer, npm). For Shopware 6 from 6.6.1 also the update mode, which brings the shop to a chosen Shopware version (maintenance mode, backup, updating plugins and switching them off temporarily, updating Shopware, switching plugins on again, restoring themes on the sales channel), optionally first as a trial run in staging, then on live with your confirmation, and single plugin updates for live and staging. For WordPress, WooCommerce and Magento, WebDonkey only shows updates; you update in staging or the local copy and push the extension;
• matching the installed versions against public databases of known vulnerabilities (OSV.dev, Packagist, npm, Shopware; for WordPress Wordfence with your own key) and file checksums on the live server;
• visual comparisons of the home page and up to ten further pages in several screen widths;
• flow tests that click through a website like a visitor; against live they stop before the buy button and never place an order, make a payment, register or send a form;
• monthly report as PDF with your sender details and logo, and a status page as an HTML file without script and without tracking;
• storage space: before staging, pushing, transferring files, backups, restoring and fetching locally, WebDonkey checks the free space on the server (also the account's quota) and on the Mac against the need plus a reserve (15 %, at least 500 MB). If it is not enough, the run does not start; if it gets tight, WebDonkey warns; during the run it shows the space and reports an abort because of a full disk in the notifications. You can delete older backups there, but not those of the latest push or of an open Shopware update;
• replacing personal data on the server as early as fetching locally (section 6.3).

Supported systems (as of this version; the app shows the current status for each system and version range):

Ranges with the status “preview” are built but not yet fully tested; there you confirm once more before every write to live. New versions stay locked until they have been tested.

Limits:

• Only supported object types are pushed, only changed fields and only between environments with the same system and extension versions. Data of extensions in their own tables is only pushed if WebDonkey knows it.
• Vulnerability matching only finds vulnerabilities listed in the sources named; it does not replace a security audit or a penetration test. File checksums find changed or new files but no malicious code in the database.
• The backups are on the same server as the website and do not replace a backup in another location.
• Scheduled checks only run once you have chosen a time for them per website, and only while WebDonkey is running on the Mac; WebDonkey catches up on anything missed at the next start. If a scheduled flow test fails while your Mac has no internet connection, the result is in the history, but WebDonkey does not notify you of it.
• Monthly report and status page show only what was measured.

Requirements: a running WebDonkey Premium licence to which the package is assigned (Premium is not included); a company account; SSH access with shell and PHP on the website's server; for staging a folder, an empty database and a (sub)domain that you create in your hosting panel; for Shopware's update mode and for plugin updates in which Composer updates packages, Composer 2 and the PHP functions proc_open or exec on the server's command line; for visual comparisons and flow tests a Chromium browser such as Google Chrome on the Mac; for matching WordPress your own key from Wordfence.

End: If no running maintenance package is assigned to a running WebDonkey Premium licence any more, for example because the package or the licence has ended, the functions of the maintenance package are locked. What happens to the maintenance package and its add-ons when their carrier ends is set out in section 3. Even then you can still view maintained websites, view, restore and delete older backups, undo pushes, delete staging and archive websites. Backups on your servers remain there until you delete them.

6.3 Fetching locally in Free, Premium and with the maintenance package

Without the maintenance package the website's personal data comes to your Mac unchanged; the app asks for your confirmation beforehand. The replacement is pseudonymisation, not anonymisation: record numbers, order contents and administrators' accounts remain.

7. WebDonkey Pages

7.1 What Pages is

WebDonkey Pages builds websites on your Mac in a conversation with an AI, checks them after every change and publishes them to your server or as a ZIP file. Each website is a folder on your Mac. Pages runs on its own; with WebDonkey on the same Mac you also get a local test with PHP, the themes from WebDonkey and taking over the licence key.

7.2 Free scope

• one active website with the full range of functions: chat, pages and sections, your own photos, checks, history of states, templates for legal notice and privacy policy;
• publishing by ZIP export only; the exported website contains the text link “Built with WebDonkey Pages” to webdonkey.io in its footer, which is part of the Free scope;
• taking over themes from the gallery.

7.3 Pages plans

In addition to the Free scope, every plan brings:

• the quota of active websites from the table, extendable with Pages add-ons; for more than 50 websites we make an individual offer on request;
• publishing directly by SFTP to your web space or server, with a check of the connection and of the server fingerprint; on Debian and Ubuntu servers with shell access, optionally setting up the web server Caddy with HTTPS via Let's Encrypt;
• the website footer without the link “Built with WebDonkey Pages”;
• submitting your own themes to the theme gallery.

No Pages plan includes WebDonkey Premium, and WebDonkey Premium includes no Pages plan.

Quota: All active websites including drafts count; archived ones do not. Archiving frees the place; the website is kept as a ZIP and can be reactivated as soon as a place is free. Subpages of a website are not limited. If the quota drops, the oldest active websites remain usable and the others are locked, not deleted; all websites can always be exported.

7.4 Checks and limits

Pages only publishes a state that passes the built-in checks, including Lighthouse, an automated accessibility check according to WCAG 2.2 level AA and the display on narrow screens. Pages collects missing details under “Still missing”; as long as anything is missing, Pages does not publish. The templates for legal notice and privacy policy cover the standard case described in the app and are not legal advice (Terms § 11(3)). We do not owe any particular result of the AI (Terms § 2(7)).

7.5 Requirements

In addition to section 2: Node.js version 22.12 or later; for the checks Google Chrome, Chromium or Microsoft Edge; AI access that you provide and pay for yourself: your logged-in Claude Code or your own API key with Anthropic. For publishing directly, SFTP access to your web space or server; for the local test with PHP, WebDonkey on the same Mac.

8. Bundles, terms and account types at a glance

• Bundle discount: If you order WebDonkey Pages Personal or Business together with WebDonkey Premium, or if a WebDonkey Premium subscription is already running in your customer account, the Pages subscription costs less in its first term (amount in the basket and in the order summary, rules on the “Payment and shipping” page). From the first renewal, the regular price applies.
• Term and cancellation: Monthly subscriptions renew for a month, annual subscriptions for a year, until you cancel. You can cancel at any time with effect from the end of the current term (Terms § 5).