Planned maintenance
We agree updates, backup checks, capacity reviews and alerts. Changes have an agreed maintenance window and rollback plan.
HomeSupport
NIYA / 04
Support
Infrastructure needs care after launch. Support scope, request handling and access arrangements are agreed separately.
What we agree
- Covered systems and responsibilities.
- Contact channel, working hours and response targets.
- Access, backups and critical change procedures.
- Work fees and separate infrastructure costs.
Round-the-clock cover and guaranteed response times are not included automatically; they require a separate agreement.
Requests and incidents
Include symptoms, when they started, the affected service and business impact. Never send passwords or secret keys in the form or Telegram.
System development
New users, services, migrations and integrations are assessed as agreed changes, not automatically included in basic support.
Let’s start with your task.
An existing server or a fresh start? Describe your situation and we will agree the next step.
Continue exploring
01
Services
Choose your task, from a private network to company files and email. Each solution has a dedicated page explaining the setup and indicative costs.
Explore this section ↗02Infrastructure
Where your services run, who owns the accounts and how servers, networks and backups fit together.
Explore this section ↗03Implementation
How a business task becomes a manageable system: requirements, deployment, verification and documented handover.
Explore this section ↗05Contact
Tell us about your infrastructure and the outcome you need. We will reply using your contact details to clarify the work.
Explore this section ↗