Vendor cloud is one size. If we wrote your customisations, we can host them — with a tuned SQL Server, a documented EU data location, and a migration we perform for you.
The difference between hosting and management is who wakes up when the alert fires.
Configuration, indexes and maintenance plans for ERP workloads — not installer defaults.
RDS or the Soft1 web client, with identities and permissions that follow your org chart.
VM replication on every plan, backups with an agreed RPO/RTO and periodic restore tests. An untested backup is not a backup. [VERIFY RPO/RTO]
KloudWithK infrastructure in a Greek data centre, with written location documentation for your GDPR compliance review.
Basic monitoring on every plan, extended monitoring on enterprise tiers. Alerts that reach a person.
OS and database updates in scheduled windows, tested before they reach production.
KloudWithK is a boutique cloud agency, and they are explicit about what that rules out: no shared hosting, no generic support desk. They know your stack, your traffic patterns, your campaign calendar and your peak hours — so when something happens, their AI agents already have the context and their team already knows your name.
The process runs from detection to resolution faster than a ticket would reach a queue. Watchon monitors CPU, memory, disk and network across the whole estate and spots anomalies in real time. Within seconds it generates a structured incident report — logs, root cause, impact, recommended remediation — that nobody had to write. The engineering team is alerted through the portal, SMS and Slack at once: no queue, no round-robin. Matterblaster then proposes one specific action — an IP block, a rate limit, a service restart, a WAF rule — and asks a human to confirm it. Once it is resolved, the full incident timeline and the root cause analysis stay in your dashboard.
The contract and the responsibility to you stay with us.
What happens on the platform when something goes wrong, before anyone has opened a ticket.
01
Continuous
Monitors CPU, memory, disk and network across the estate, spotting anomalies and threat patterns before they escalate.
02
Seconds
A structured incident report with logs, root cause, impact and a recommended remediation path. Nobody had to write it.
03
Instant
Portal, SMS and Slack simultaneously. No queue, no round-robin — the right engineers see it at once.
04
Matterblaster requests one specific remediation — IP block, rate limit, service restart, WAF rule — and waits for a human to confirm.
05
Metrics recover, and the full incident timeline and root cause analysis stay in your dashboard.
These times are contractual and are measured from the moment a ticket is raised.
| Tier | Response time | Channels | Coverage hours |
|---|---|---|---|
| Critical — production has stopped | 30 minutes | Phone, portal | 09:00–18:00 |
| High — serious fault with a workaround | 4 hours | Portal, email | 09:00–18:00 |
| Normal — question or change request | 1 business day | Portal | 09:00–18:00 |
Times run from the moment a ticket is raised, Monday to Friday 09:00–18:00. Infrastructure availability: 99.9% uptime SLA on every plan. Exact commitments are fixed in the contract.
A Soft1 environment is sized by database and concurrent users, so the managed tier is quoted rather than listed. The infrastructure tiers below are KloudWithK's published plans.
Recommended
On request
50 € / month
133 € / month
Recommended
200 € / month
300 € / month
500 € / month
750 € / month
Recommended
1,033 € / month
1,200 € / month
1,500 € / month
If your Soft1 is close to standard, you have no custom code and no unusual integrations, the vendor cloud is probably cheaper and entirely adequate. We will tell you that during the assessment rather than after the invoice.
Ours makes sense once your ERP has stopped being standard: custom screens and reports, integrations we wrote, a database that needs tuning for your particular load, or a requirement to document exactly where the data sits.
Put another way: if hosting it properly means knowing what has been changed inside your Soft1, that is us.
The usual experience of changing provider is a backup file and good luck. That is not how we work.
We document the existing environment, build the new one alongside it, run a rehearsal migration with real data, and agree a cutover window with a rollback plan if anything goes wrong. Downtime is agreed beforehand, not discovered afterwards.
The same team runs private clusters for e-commerce and news portals with real traffic spikes.
Private clusters with load balancers, database clustering, Redis cache and CDN.
Windows stack for .NET stores and applications, scaled on the same principles.
Corporate file infrastructure and central backups for all of the above.
NEF-NEF Homeware
Braincandy
Semeli Estate
In a data centre in Greece — inside the EU, and inside your own jurisdiction. We provide written documentation of location and subprocessors for your compliance review.
It is agreed in advance and executed in a window you choose, usually outside business hours. A rehearsal migration comes first, so the number is measured rather than estimated.
We hand over complete backups and documentation of the environment. We do not use closed formats that make moving harder.
Both, if you want. Endpoint, network and M365 support is described under IT services and goes into the same contract.
Existing infrastructure, user count, database size and what worries you. We come back with a proposed architecture and a cost.