Support / Expertise when it matters
Our aim is software you can run without us. When your team needs specialist advice, custom development or agreed operational cover, our paid services are here to help.
We earn revenue from custom consulting and engineering services, including agreed support engagements. We do not reserve product features for paying customers.
Support engagements
Every engagement begins with your requirements, the product’s current maturity and a written scope. Pricing is agreed for the work, with no per-seat software charge.
Architecture and adoption advice, evaluation planning, migration assessment and practical guidance for your own engineering team.
Scoped engineering for integrations, workflows and capabilities that help the software fit your organisation.
A separately agreed support engagement for teams that require round-the-clock availability and a defined escalation path.
24/7 coverage starts only under an agreed service contract. Sending an email does not establish coverage or a response-time commitment. Product readiness and the deployment requirements are assessed before support is agreed.
Quality is part of the product
Our development process uses automated acceptance testing and exact executable-line coverage gates for production Java code. Tests exercise implemented behavior, persistence and access boundaries; product repositories record the results and limitations.
Paid support adds dedicated expertise for your organisation. It does not replace testing, and passing tests alone does not establish security or production readiness.
See our engineering principlesNo. The products are Apache 2.0 licensed. You can use the code, operate it yourself and work with another provider, subject to the licence terms. Review each project’s current maturity before deployment.
Yes. Fork the repository, adapt it to your requirements and submit improvements through GitHub. The contribution guide in each repository explains how to get started.
Include the product, version, deployment environment, the outcome you need and any relevant non-sensitive error details. Do not email passwords, tokens or private customer records.
Email support@opensoft.ge with the product name, affected version and a safe description of the issue. Keep exploit details and sensitive information out of public issue trackers while the report is reviewed.
A successful engagement leaves you with better software, clear documentation and the knowledge to move forward.