Browser-based form designer
Place text fields, check boxes, radio buttons, drop-down lists, images, lines and signature fields by drag and drop. Set fonts, colours and validation rules.
Read moreIn short
- What: a web-based eForms server. One design in the browser becomes a fillable PDF (AcroForm), responsive HTML and static HTML.
- Output: every submission is a sealed PDF (SHA-512 server signature, optional RFC 3161 timestamp) plus XML data, delivered by e-mail.
- Extras: handwritten and X.509 signatures, ZUGFeRD / XRechnung e-invoices, EU Digital Identity Wallet sign-in, REST API and webhooks.
- Where: in your own data centre (Windows Server, IIS, .NET Framework 4.7.2) or hosted by Aloaha Limited, Malta (EU).
What the eForms Server does
CodeB eForms Server turns paper and PDF forms into online forms that work on every device. Form designers build the form in a browser-based WYSIWYG editor. Citizens, customers or staff fill it in on a phone, a desktop browser or in Adobe Reader. The server checks the input, renders the result and sends it to the person who submitted it and to the business owner of the form.
It is built for public administration, insurers, property and legal offices, universities and companies that need forms with a reliable paper trail: signed, timestamped and readable by people and by software.
What you get
The main building blocks. Each one is described in detail on its own page.
PDF and HTML from one design
Every released form exists as dynamic PDF, responsive HTML and static HTML. The server picks the right format for the device.
Read moreHandwritten and X.509 signatures
Sign with finger or mouse; the server seals the result. Fields named esignature become PDF signature fields for certificates and smart cards.
Read moreE-mail delivery with XML data
The submitter gets the sealed PDF, the form owner gets the PDF plus the data as XML. Mail texts are templates per language.
Read moreZUGFeRD and Factur-X
Turn invoice forms into EN 16931 e-invoices: PDF/A-3 with embedded XML, created automatically on submission.
Read moreUsers, groups and sign-in
Roles for administrators, designers and guests, form groups, and sign-in with your Aloaha or CodeB account (OpenID Connect), including passkeys and the EU Digital Identity Wallet.
Read moreHow a form goes live
Four steps from idea to the first submission.
- Design. Create a new form or clone an existing one, place the fields and set validation rules in the online designer.
- Preview and release. Check the PDF preview, then release the form. The server renders the dynamic PDF and both HTML versions and e-mails you when they are ready.
- Share a link. Put the form link on your website, in an e-mail or on a QR code. No plug-in and no app are needed.
- Receive submissions. Each submission is sealed as PDF and sent by e-mail together with the XML data, ready for your back office.
Privacy by design
The eForms Server does not keep a database of submitted forms. A submission is turned into a sealed PDF and XML, delivered by e-mail and then removed from the server. If you need a server-side copy, an optional encrypted archive keeps password-protected PDFs that can only be opened with the submission ID.
Because you can run the server in your own data centre, form data never has to leave your infrastructure.
Own eForms server or form-builder service?
What differs between running the CodeB eForms Server and a typical hosted form-builder service. The right choice depends on your data, your documents and your processes.
| Question | CodeB eForms Server | Typical form-builder service |
|---|---|---|
| Where do the data live? | In your own data centre, or on a server hosted by Aloaha in the EU (Malta). | On the provider's cloud. |
| What does the submitter get? | A sealed PDF of exactly the form they filled in. | Usually a confirmation e-mail or web page. |
| Paper and PDF layout | The form keeps the layout of the paper or PDF original, plus a responsive version for phones. | Usually a web-only layout. |
| Signatures | Handwritten signature sealed by the server; X.509 signature fields for certificates and smart cards. | Often a drawn signature image or an add-on. |
| E-invoices | ZUGFeRD / Factur-X and XRechnung from a form or through the API. | Rarely built in. |
| Identity | Sign-in with OpenID Connect, passkeys and the EU Digital Identity Wallet; forms pre-filled with verified data. | Varies. |
| Integration | REST API (OpenAPI 3.1) with OAuth 2.0 bearer tokens, signed webhooks, XML for every submission. | REST API and webhooks are common. |
Frequently asked questions
Is the CodeB eForms Server the same as the Aloaha eForms Server?
Yes. The Aloaha eForms Server was renamed CodeB eForms Server in October 2026. It is still made by Aloaha Limited in Malta.
What is CodeB eForms Server?
A web-based platform to design, publish and process electronic forms. One design is published as fillable PDF, responsive HTML and static HTML; submissions are delivered as sealed PDF plus XML by e-mail.
Do form users need Adobe Reader or an app?
No. The responsive HTML version works in any current browser on phones, tablets and desktops. The dynamic PDF version is available for people who prefer Adobe Reader.
Can forms be signed?
Yes. Handwritten signatures are captured with finger or mouse and sealed by the server. Forms that require sign-in can be signed with the signer's own key at the CodeB server, others receive your organisation's seal, both as PAdES up to B-LTA. Fields named esignature become PDF signature fields for X.509 certificates and smart cards.
Where are submitted data stored?
By default nowhere: the submission is delivered by e-mail as sealed PDF and XML and then removed. An optional encrypted archive can keep password-protected copies.
Can I run it in my own data centre?
Yes. The server runs on Windows Server with IIS and the .NET Framework 4.7.2. Aloaha can also host it for you.
How is the eForms Server licensed? Is there a trial?
You can use the eForms Server hosted by Aloaha or rent a server for installation in your own data centre; rented in-house servers receive free updates, and integration help and online training are free. A free 30-day trial with three example forms is available. For prices, write to info@aloaha.com.
Can I send e-invoices without my own invoicing software?
Yes. Design your invoice template once on the eForms Server and fill it in for each invoice; every submission becomes a compliant ZUGFeRD / XRechnung e-invoice (PDF/A-3 with EN 16931 XML), sent by e-mail.
Can the eForms Server create e-invoices?
Yes. Invoice forms can be converted to ZUGFeRD / Factur-X (EN 16931) on submission: a PDF/A-3 with the embedded invoice XML.
Is the CodeB eForms Server a form builder?
It is a form server: you build forms in its browser-based designer like in a form builder, but every form also exists as fillable PDF, every submission is a sealed PDF plus XML, and you can run the server yourself.
Does the CodeB eForms Server have an API and webhooks?
Yes. A REST API described as OpenAPI 3.1 lists forms and fields, validates, fills and submits forms and creates e-invoices; webhooks send every submission as signed JSON to your system.
See it with your own forms
Try the public sample forms, or ask us for a free online presentation or a free 30-day trial.
Last updated: