Pages, emails, and decks — designed in-house.
Create the business material inside the workflow that will publish, send, or reuse it.
A creation studio with three editors behind one library: a drag-and-drop page builder, an email designer for invitations, and a deck editor that presents and exports. It is the same engine your Events registration pages and HR templates are built with.
For operations teams creating registration pages, invitations, internal documents, and presentation decks.
Create in the same system that publishes the work.
Create the business material inside the workflow that will publish, send, or reuse it.
Web page
Responsive blocks
Merge fields
Deck
Present and export
Document
Stop rebuilding business context inside a separate design tool.
The editors use blocks and direct manipulation, while the owning app handles the final operational action.
Build pages from blocks
Sections, text, images, and forms — dragged into place with device preview, undo, and autosave. No code.
Emails guests actually open
Invitation-ready blocks with live preview; sending happens from the guest list, with merge fields filled per guest.
Decks that present themselves
Slides with templates, speaker notes, drag-reorder, keyboard presenting, and PNG export per slide.
Your work is protected
Autosave with visible states, an editing pause when a draft cannot be read safely, and delete-with-restore on slides.
Powers the other apps
Events registration pages and HR document templates are Seaforge documents — publish them from the app that owns them.
The mechanisms behind Seaforge.
Not features — the guarantees. Each one is enforced in the product rather than promised in a policy.
- Server-persisted documents
- Pages, emails, and decks are stored records in your organization, not files on someone’s laptop. Access follows the same permissions as everything else.
- Autosave with a visible state
- The editor shows whether the draft is saved, saving, or conflicted. Undo and restore exist because “did that save?” should never be a guess.
- The owning app publishes
- Seaforge composes; Events publishes the registration page and HR reuses the document template. The operational action stays with the module that owns the data.
- Personalised from real records
- Guest, event, and employee fields come from the live record, so a re-send does not mean re-typing the same merge fields into a new copy.
Better together.
The modules share one organization record — connections are built in, not integrations to configure.
Create the material where the business will actually use it.
Put Seaforge to work inside the same platform as the rest of your operation.