Veylor is a technical collective engineering high-integrity, sovereign software. We build resilient digital tools for individuals and independent teams who refuse to outsource their infrastructure to Big Tech.

Our philosophy is anti-bloat: zero AI slop, zero cloud lock-in, and zero monthly subscriptions. We engineer local-first, open-source platforms designed to last as long as the hardware they run on. You buy the software once, you own the code, you control your data.

All Veylor initiatives adhere to a strict set of architectural mandates:

• Sovereignty-First (Local-First): Systems must maintain full operational capacity in disconnected or air-gapped environments. We prioritize local data persistence and CRDT-based synchronisation over cloud dependency.
• Hardened Security: Security is integrated into the core logic via zero-trust architecture, end-to-end encryption (AES-256), and verifiable audit trails.
• High-Density Utility: We reject consumer-grade UI abstractions. Our interfaces prioritise information density, low-latency data visualization, and professional-grade telemetry.
• Privacy by Architecture: Data is treated as a strategic asset. Veylor software minimises metadata leakage and ensures the user retains absolute ownership of the generated intelligence.

Some services developed under Veylor-umbrella might be temporarily closed-sourced to protect Intellectual Property and important architectural choices that might threaten our customers.

• eGarage App: The modern platform for automotive workshops. Design custom inspection checklists, log car histories, manage client files, and share professional digital reports instantly.
  Initially developed as Velo, app for car enthusiasts and people that want to track their fuel expenses, service records and mileage; Later, eGarage was born as B2B alternative, app that has similar functionality but tailored more towards GMS and Digital Inspections, it uses same API, we call it Velo-Core, so source code is temporarily closed but in a future, Velo will be released as fully open-source app for anyone to access it, required parts of velo-core would be available as well
  More about Velo https://ihorsavenko.com/projects/velo/
  As for eGarage - very likely it will remain as closed-source application, or be partially open-source, but those options aren't currently considered.

Repositories might look inactive for solid periods of time, but due to limited time and resources - some projects may be prioritised higher due to various reasons. Current focus of Veylor goes to establishing digital presence, and forming eGarage as autonomous profitable product, that will cover future expenses of Veylor's projects and experiments.

Current Veylor ecosystem consists of specialised modules designed for integration:

• relay: A secure, privacy-first notification routing microservice featuring GDPR-compliant recipient synchronisation, content redaction, and a hybrid gRPC/REST architecture. Used by all Veylor projects.
• sentinel: A Tier 1 personal operations management system (C2) designed for field coordination and mission planning.
• editor: A minimalist, high-performance text environment for macOS, optimised for secure documentation and configuration.
• satcomsim_federated: A federated simulation framework for modeling satellite constellations and complex communication nodes.
• veylor-documents: Technical specifications, whitepapers, and Veylor design guidelines.
• More to be added: We're actively looking to expand our ecosystem by various services

Veylor is an open-source initiative that values technical precision and peer review. We invite collaboration from developers and engineers who prioritise stability and performance over industry trends.

1. Repository Audit: Review the technical stack to identify relevant modules.
2. Implementation: Clone repositories for local deployment. Veylor projects are designed for Docker-based or native binary execution.
3. Technical Contribution: We accept pull requests that improve system resilience, reduce latency, or enhance security protocols.
4. Issue Reporting: Utilise GitHub Issues for technical bug reports or feature requests based on operational requirements.

Veylor HQ projects are distributed under the Apache License 2.0 or the MIT License. These licenses ensure that Veylor software remains a transparent and accessible foundation for independent operations.