Skip to content
About us

We build and maintain Automail.

Lineverge is a software engineering company based in Singapore and Hong Kong. We develop Automail for supply chain data collection, automation, and analytics.

Our priority is performance, stability, usability, and keeping the software efficient and affordable to operate.

Lineverge supply chain collaboration network
Our people

Meet the team

Florian Gamper

Florian Gamper

Managing Director

Software architect with supply chain consulting & strategy background, passionate programmer. MBA from CUHK.

Kerry Chan

Kerry Chan

Product Manager

Product specialist with an engineering background, enjoy building and refining data products to amplify business value. HKU graduate.

Melody Feng

Melody Feng

Data Scientist

Data Scientist striving to leverage data and analytical skills to optimize supply chain workflows. Masters in Data Science from the University of Chicago.

Ian Lee

Ian Lee

Data Engineer

A data-driven person who likes to solve problems with software engineering. Bachelor in Data science from HKUST.

Hyder Ali

Hyder Ali

Software Engineer

A passionate technologist, driven to use programming & analytical skills to create transformative solutions. Bachelor of Engineering from the City University of Hong Kong.

HOW WE WORK

A technical team focused on the product.

Our primary focus is developing Automail and continuously improving its stability, reliability, performance, usability, and running cost. We want the software to work well and remain affordable as each project grows.

01 / PRODUCT ENGINEERING

Keep making Automail better.

Our engineers spend most of the time building, maintaining, testing, and refining Automail. Improvements to existing features are as important as adding new functionality.

StabilityPerformanceReliabilityCost efficiency
02 / PROJECT DELIVERY

Engineers work directly with project teams.

During deployments and subsequent adjustments, each Lineverge team member communicates directly with the customer's core project team. Requirements, feedback, and issues reach the people implementing changes, so the software works as expected.

RELEASE HISTORY / 2019 - 2026

Automail, version by version.

From workflow automation and configurable tables to integrated AI and a purpose-built interface, Automail has evolved through regular product releases.

CURRENT VERSIONv14.1Automail
2019 3 releases
2019 / AUTOMAIL

Foundations

The core application, access controls, and workflow engine.

MAJOR RELEASEv1.0

Initial release

Initial release of Automail.

v2.0

Introduced reusable class-based views and access controls for frontend components.

v3.0

Introduced the Flows module for background workflows.

2020 3 releases
2020 / AUTOMAIL

Early automation

Configurable email automation and shared application utilities.

MAJOR RELEASEv4.0

Email automation

Launched the configurable Automail email-automation module.

v5.0

Refactored shared code across modules.

v6.0

Added common utility functions.

2021 5 releases
2021 / AUTOMAIL

Interfaces and processing

Interface updates, processing engines, and file handling.

MAJOR RELEASEv7.0

Interface redesign

Redesigned the interface using Bootstrap 3 and a new application layout.

MAJOR RELEASEv8.0

Engine upgrade

Upgraded inbound and outbound processing engines.

v8.1

Applied security fixes.

v8.2

Updated the user interface.

v8.3

Added support for reading CSV and Pickle files.

2022 12 releases
2022 / AUTOMAIL & AUTOFORM

Autoform and platform expansion

Introducing Autoform alongside new Table features, data exchange capabilities, SSO, and deployment tooling.

MAJOR RELEASEv9.0

Introducing Autoform

Introduced Autoform for structured data collection and refactored menu and search configuration.

v9.1

Added ad hoc Excel downloads.

v9.2

Introduced the Table module.

v9.3

Added smart CSV and Excel uploads to tables.

v9.4

Updated Autoform endpoints and synchronization functions.

v9.5

Extended table rendering and resolved related issues.

v9.6

Removed the legacy projects directory.

v9.7

Consolidated deployment files and moved documentation to GitBook.

MAJOR RELEASEv10.0

Deployment restructuring

Reorganized deployment configuration and added serverless.yml for containerized deployments.

v10.1

Retired the legacy app_table component.

v10.2

Added serverless deployment scripts.

v10.3

Added OpenID-based single sign-on.

2023 7 releases
2023 / AUTOMAIL

Scale and orchestration

Data synchronization, exports, Airflow, and infrastructure automation.

v10.4

Introduced generic synchronization between Automail and Autoform.

v10.5

Upgraded the Table upload module.

v10.6

Added multi-sheet Excel exports with configurable and conditional formatting.

v10.7

Introduced bulk Autoform session retrieval with approximately 1,000x faster loading.

v10.8

Integrated Airflow into containerized deployments.

v10.9

Added Terraform deployment scripts for Elastic Beanstalk and cron.

MAJOR RELEASEv11.0

Infrastructure automation

Introduced Terraform deployment scripts using ECS and Airflow.

2024 6 releases
2024 / AUTOMAIL

Automail v12

A refreshed interface and new workflow capabilities.

MAJOR RELEASEv12.0
September 2024

Major UI upgrade

Upgraded the interface to Bootstrap 5, updated jQuery, and refreshed frontend libraries.

v12.1

Updated Terraform deployment scripts.

v12.2

Added Leaflet for advanced map rendering.

v12.3

Introduced the Custom Email module.

v12.4

Optimized frontend saving in the Table module.

v12.5

Added automatic recovery for Autoform synchronization.

2025 15 releases
2025 / AUTOMAIL

Automail v13

A rebuilt data table, OCR improvements, and integrated chat.

v12.6

Rebuilt the DataTable module.

v12.7

Added ZIP downloads.

v12.8

Introduced the Chat app.

v12.9

Added the OCR extraction app.

v12.10

Upgraded Django to version 4.2.

v12.11

Switched the administration interface to the default Django theme.

v12.12

Reduced the operating cost of containerized deployments.

v12.13

Added a generic pivot-table option.

v12.14

Extended OCR support with generic and custom configurations.

v12.15

Introduced group emails combining related monitor items.

v12.16

Upgraded Leaflet mapping for performance and additional features.

v12.17

Added Elastic Beanstalk deployment scripts.

MAJOR RELEASEv13.0
October 2025

Integrated chat

Launched integrated chat in Automail.

v13.1

Added compact tables with loading statistics.

v13.2

Moved chat to the Responses API for newer model support.

2026 8 releases
2026 / AUTOMAIL

Automail v14

A purpose-built interface, history, and continuing refinements.

v13.3

Added tech-pack support to the OCR app.

v13.4

Optimized the deployment process.

v13.5

Added an Elastic Beanstalk scheduler option to reduce UAT costs.

v13.6

Replaced the Hyper theme with the built-in Automail theme.

v13.7

Added a compact DataTable mode.

v13.8

Prepared the application for history functionality.

MAJOR RELEASEv14.0
September 2026

Modern interface

Introduced a purpose-built modern interface, contextual chat, history, and desktop-style interactions.

v14.1
CURRENT RELEASE

Added table Excel exports, fixed UI issues, and improved performance.

Our tech stack

Engineering built around the problem

We use different architectures and technologies where they make practical sense. Our focus is on maintainability, flexibility, performance, and the ability to adapt quickly to changing business requirements.

Automail Architecture

Automail uses a deliberately monolithic application architecture, organized into modular components. This gives us a stable common foundation while allowing business logic, workflows, interfaces, and integrations to be extended quickly where a project requires something specific.

Serverless Autoform

Autoform is an AWS-hosted SaaS application with a static frontend, serverless backend, and document-oriented data storage. AWS Step Functions orchestrate multi-step workflows, allowing the service to scale independently while remaining lightweight for external supply chain partners.

Data Processing & ML

We maintain our own data-processing and machine-learning algorithms for recurring transformation, matching, classification, and loading tasks. They are designed around the supply chain datasets we work with and optimized for processing large volumes efficiently.

Document Intelligence

Our document-processing pipelines use multiple LLM stages to extract, interpret, normalize, and clean information before it enters Automail. The process can combine model reasoning with deterministic validation and document-specific business rules rather than relying on a single extraction prompt.

Contextual AI

Automail includes an integrated chat using large-context models such as GPT-5.6 Sol or Gemini 3.8 Flash. The integration is aware of the structure and capabilities of each Automail instance and can work directly with application data and tools without requiring a separate RAG infrastructure.

Continuous Refactoring

Every major Automail version includes architectural cleanup and refactoring alongside new functionality. We continuously apply established software design patterns where they improve separation of concerns, reuse, testing, and long-term maintainability.

Supply Chain Document Processing

Automail uses a deliberately monolithic application architecture, organized into modular components. This gives us a stable common foundation while allowing business logic, workflows, interfaces, and integrations to be extended quickly where a project requires something specific.

Invoices Purchase Orders Bills of Lading Delivery Notes Packing Lists Country of Origin Certificates Scope Certificates Transaction Certificates Business Registrations Technical Sheets Inspection Reports Test Reports Color Approval Records Certificates of Analysis Tech Packs

Engineer-Owned Codebase

Our application architecture and production code are designed, written, reviewed, and maintained by our engineering team. We use AI development tools selectively for bounded tasks where they improve efficiency, such as small extensions, repetitive transformations, or test support. They supplement the engineering process rather than replacing ownership of the codebase or our security and review practices.

Designed to Evolve

New capabilities are introduced without treating existing deployments as disposable. Architecture, migrations, and backward compatibility are considered as the platform evolves.