ASK-Solutions

Why Synergos existed

BackPage had shown the value of generating websites from structured source material. Synergos grew from that foundation and explored how the same ideas could support more complex sites. It was used to think about pages, products, ordering, navigation, reuse of structured content and the relationship between publishing and practical activity.

The name Synergos reflected the idea of bringing publishing and practical exchange together. At the time, selling something online often started with publishing clear information about what had been made: a catalogue page, a product description, photos, prices, options, availability and contact details. The purchase itself might then continue by email, fax or a physical visit. Synergos explored that bridge between publishing information and enabling exchange, before the later project line moved away from marketplace features and focused more clearly on maintainable source-based publishing.

Publishing, products and ordering

Synergos explored a more interactive publishing model than BackPage. Where BackPage generated static pages from source files and GNU tooling, Synergos moved structural data, page information, product information and images into an SQL database. It provided a login-based editing flow where pages and product information could be maintained through a web interface instead of only through source files and command-line generation.

The system also experimented with WYSIWYG page editing at a time when web-administered CMS tooling was not yet readily available for small, practical websites. Most people still had to edit HTML directly, use desktop web-authoring tools, or depend on someone else to update pages, product descriptions, images and ordering information. TYPO3 existed, but was not easy to install, configure or use for the kind of practical publishing and catalogue work Synergos was trying to support.

Synergos was not only a publishing experiment. It tried to bring page editing, product presentation, ordering and payment into one practical web-administered system. For its time, that was a serious attempt to make small-scale online publication and sales more manageable: publish what was made, maintain the information, present images and options, receive orders and connect payment without rebuilding a separate workflow for every site.

The longer-term maintenance burden became the problem. Payment handling was not just a one-time addition. PayPal, iDEAL and MrCash each needed ongoing integration work, and Dutch iDEAL was especially demanding because banks had their own implementations. Keeping those payment paths working, tested and compatible increasingly moved time and attention away from the foundation’s wider mission: shared knowledge, free software, documentation, technical education and public-benefit work.

This experience helped clarify the later Nocterra direction. Synergos showed what was possible, but it also showed why scope control matters. Nocterra kept the maintainable publishing lessons while deliberately leaving behind the payment, marketplace and webshop-maintenance burden.

Licence history

Synergos was released as free software. The early public releases used the GNU General Public License version 2, following the same free-software line as BackPage. Around 2008, Synergos moved to the GNU General Public License version 3.

The move from GPLv2 to GPLv3 was important because the foundation’s free-software position is based on the four essential freedoms: the freedom to run, study, share and modify software. For ASK-Solutions and the IRADIS Foundation, those freedoms are not only legal permissions on paper. They must remain usable in practice.

GPLv3 addressed problems that had become clearer after GPLv2 was written, including Tivoization: distributing GPL-covered software in a device while preventing users from running modified versions on that same device. For the foundation, that mattered because technical, legal or contractual restrictions that make modified software unusable weaken the practical meaning of free software. The move to GPLv3 therefore fitted the wider mission: software should remain available to study, adapt, improve, reinstall, preserve and share.

Historical Synergos releases should be read together with the licence files included in those releases, especially where restored archives contain material from different periods.

The Great Server Crash™ and the move to Nocterra

In 2019, after The Great Server Crash™, Synergos was not repaired as it was. The failure became a turning point. Instead of restoring the old system unchanged, the useful ideas were carried forward into a renamed and rewritten project: Nocterra.

Nocterra kept the emphasis on maintainable source-based publishing, but with a clearer direction: free software, long-term control, privacy, security, accessibility, no browser-accessible administration backend, no telemetry and no open-core model.

Relationship with ASK-Solutions

Synergos belonged to the wider ASK-Solutions line of work around shared knowledge, practical publishing and free software. It explored a broad practical question: how can people publish information, present work, maintain pages, organise product or catalogue data, receive orders and connect payment in a way that remains understandable and manageable?

That question fitted the foundation’s work at the time. Publishing information online was becoming part of how people explained projects, shared knowledge, presented creative or technical work, and made contact with others. Synergos tried to bring those activities together in one web-administered system, combining page editing, structured data, images, ordering and payment handling.

The project also became an important learning point for later work. Synergos showed that making a publishing system more interactive and complete also creates a larger and more fragile maintenance surface. Login screens, authoring pages, upload handling, session management, WYSIWYG editing, database state, libraries, payment integrations and the PHP runtime all became part of what had to remain secure and compatible over time. That was not simply a question of capable maintainers. A browser-accessible administration environment depends on many moving parts, and PHP’s loose language design, historical quirks and large ecosystem made it a weak foundation for something that required a very high security margin.

Those lessons helped shape the later Nocterra direction. Nocterra kept the useful publishing lessons, but moved away from live browser-based administration, database-backed authoring, payment handling and webshop-maintenance scope. The later model favours source-based publishing, predictable generated output, fewer exposed attack surfaces, long-term maintainability and clearer boundaries around what the CMS itself should be responsible for. Instead of making authoring depend on a CMS-owned browser backend, Nocterra allows authoring and deployment to use established tools and protocols such as SSH, SCP, SFTP, rsync and WebDAV, leaving site owners free to choose their editor, workflow, operating system and access method.

Status

Synergos is a historical project. It is no longer the current publishing system, but it remains part of the project lineage that led to Nocterra. Its role today is to document that transition and explain why Nocterra was written the way it was.

Where to go next

• BackPage — earlier publishing system from which Synergos evolved.
• Nocterra — current free software publishing system.
• The Great Server Crash™ — historical chapter behind the rewrite.
• History — wider history of ASK-Solutions and the IRADIS Foundation.