How is Licko App different from an e-mail client?
Licko App does not work with digital correspondence. It is focused on physical mail workflows: printing, tariffs, shipments, tracking, and operational processes around them.
Software platform for operational work with physical mail and postal workflows: letters, envelopes, printing, tariff handling, tracking, and integrations with postal services. In practice, it is a unified environment where a team manages shipments from preparation to status handling within a single operational workflow instead of relying on fragmented manual steps.
The goal of the platform is to make physical mail a manageable, transparent, and repeatable process: clear statuses, less operational randomness, centralized management, and a foundation for further automation.
Who it is for:
Companies, offices, legal teams, NGOs, and service organizations that systematically work with large volumes of correspondence, documents, and shipments.
Physical mail in Licko App is treated not as a collection of disconnected manual actions, but as operational infrastructure.
The platform is described through the concept of a “mail operations layer” — a digital layer that standardizes, structures, and automates traditional postal workflows between people, equipment, and external postal services.
The development direction includes further expansion of:
Licko App (the platform web portal) is the operational interface for teams: shipment management, statuses, dashboards, and daily postal operations in one place. It centralizes process data and events (shipment objects, history, statuses) that provide transparency and operational control.
Porto SDK is a toolkit for embedding the platform into external systems (internal company services, CRM/ERP systems, custom dashboards). The SDK allows teams to connect postal workflows to their infrastructure, automate shipment creation and processing, integrate printing, scanners, and tracking, work with events and statuses, and build custom operational scenarios where the portal alone as a UI is not sufficient.
In short: Licko App is the operational workspace for people and operational data; Porto SDK is the bridge for integrating and automating these operations inside your systems.
The platform is designed as a modern operational SaaS with a focus on:
The platform is currently under active development as an independent software product within gruncellka (Berlin, Germany). Public launch, beta access, and the scope of the first release are subject to the roadmap; functionality and integrations may evolve iteratively over time.
Contact / collaboration: official contacts and imprint details — see the impressum.
Licko App does not work with digital correspondence. It is focused on physical mail workflows: printing, tariffs, shipments, tracking, and operational processes around them.
A postal operator handles delivery and shipment logistics. Licko App is not a delivery service — it is a software infrastructure layer above postal services.
The platform helps organize, standardize, and automate postal operations between teams, documents, printing, tracking, and external postal services within a unified operational workflow.
Licko App can integrate with multiple operators and services, but it does not replace physical delivery itself.
It is a digital layer above physical mail that unifies steps, data, and statuses as if mail were part of a company’s operational system rather than simply “taking a letter to the post office.”
Licko App is for the team’s daily operational work inside the platform interface.
Porto SDK is for integrating the same workflows into CRM systems, internal portals, backends, or custom operational systems.
The set of supported workflows, operators, and countries depends on the product stage and available integrations.