Living In New Innovation And Networked Technological Trends
Building focused engineering organizations, technology products, and platforms across software, infrastructure, fintech, Linux, media, and design.
Liniantt is the parent organization behind a growing collection of focused engineering, technology, and product initiatives.
The name represents:
Living In New Innovation And Networked Technological Trends
Our work spans software engineering, Linux systems, infrastructure, financial technology, media, design, research, developer tooling, and digital products.
Rather than placing every idea or product under one identity, Liniantt provides the umbrella while individual organizations develop their own technical focus, products, communities, and engineering direction.
|
Linux · Automation · Developer Tooling Linux-focused engineering and open-source tooling. LinuxEuphony builds practical tools around Linux systems, workstation automation, infrastructure utilities, diagnostics, Proxmox, shell tooling, and developer productivity. |
🏠 loftInfrastructure · Homelab · Systems Engineering Infrastructure engineering, experimentation, and self-hosted systems. loft focuses on networking, compute, virtualisation, storage, resilience, monitoring, automation, and infrastructure documentation. Leverage · Orchestrate · Federate · Test |
◈ FinvoneFintech · Product Engineering · Financial Technology (FIN)tech, e(VO)lution, engi(NE)ering Engineering the Evolution of Fintech. Finvone is focused on serious fintech products, research, financial platforms, and product engineering. |
|
Media · Production · Digital Products A media production initiative focused on digital media products and services. Products and platforms are developed independently under the PhotoVendor identity. |
Art · Design · Creative Technology A creative and design-focused organization exploring products at the intersection of art, design, and technology. |
Liniantt also serves as a home for software products and engineering initiatives that do not require a dedicated organization of their own.
Our product engineering approach emphasizes:
- Clear product ownership
- Maintainable architecture
- Strong backend foundations
- Reusable platform components
- API-first integration
- Security and reliability
- Documentation
- Long-term maintainability
Open-source software remains an important part of the Liniantt ecosystem.
DuesClerk is a platform for managing dues for personal and business use.
| Repository | Description | Technology |
|---|---|---|
| duesclerk-mobile | Mobile application for managing personal and business dues. | Kotlin |
| duesclerk-backend-api-service | Backend API service for the DuesClerk platform. | Java / Spring |
The following repositories represent earlier generations of the DuesClerk platform and remain available for historical and technical reference.
| Repository | Description | Technology |
|---|---|---|
| duesclerk-android-legacy | Legacy Android implementation of DuesClerk. | Java |
| duesclerk-backend-legacy | Legacy backend implementation of DuesClerk. | PHP |
Across the Liniantt ecosystem, our work generally falls into several engineering domains.
Backend services, APIs, distributed applications, product platforms, shared components, and integration architecture.
Linux automation, workstation tooling, shell utilities, diagnostics, and system engineering.
Networking, virtualisation, compute, storage, self-hosting, resilience, monitoring, and operations.
Financial platforms, fintech product research, automation, risk, payments, lending, investing, and financial systems.
Media production, design, digital content, and technology-enabled creative products.
We aim to build technology that is:
Purposeful
Technology should solve a real problem or enable a meaningful capability.
Maintainable
Systems should remain understandable and operable long after their initial implementation.
Reliable
Engineering decisions should account for failure, recovery, observability, and operational reality.
Modular
Products and platforms should have clear boundaries and evolve without unnecessary coupling.
Documented
Architecture, decisions, systems, and operational knowledge should not exist only in people's heads.
Evolving
Technology changes. Our systems and engineering practices should be able to change with it.
