Secure IT supportfor your company.
In thirteen years in this trade we have learned that for the client the important part starts the day after launch, when something has to be fixed, added or repaired quickly.
We do not stop
at handing over files.
Servers, deployments, backups and help after launch we do in house. This is not an extra line on a price list, it is the reason we never have to hand the deployment to anyone else and never end up explaining somebody else’s hosting.
| Environment | We set it up and configure it ourselves, no shared hosting with accidental neighbours |
|---|---|
| Deployment | Automated, repeatable, with a way back from a change |
| Backups | Daily, checked for restore and not only for completion |
| After launch | Updates, monitoring and contact with us, not with a helpline |
We roll them out
and train the team.
A system changes nothing on its own until people know what to turn it on for. That is why a rollout ends here with training, not with a login sent by email.
| Helpdesk | Requests in one place instead of in the inboxes of several people. We set up queues, priorities and who sees what |
|---|---|
| Sales and warehouse | We set up sales and warehouse systems: records, documents, permissions and the flow between them |
| Training | On your data and your processes, not on the sample database from the vendor manual |
| After the training | A step by step write-up stays with the team, and we stay reachable when someone gets stuck |
What it looks like
from your side.
You write to us, not to a ticket system, and you get an answer from the same person who built your site.
We take on as many projects as we can run carefully, so you are not a number in a queue and you do not wait for your turn.
During and after
| During | You watch the progress on a live link, not on screenshots in a PDF. You raise comments at any moment, not at one appointed presentation |
|---|---|
| Response time | Agreed at the start and written into the contract, so you have it on paper instead of in a promise. Outages have their own, shorter deadline |
| Changes after launch | Small fixes within the care plan, bigger things we quote separately and tell you about before we start |
And if we are gone?
| Technologies | Standard and widely known: SvelteKit, Node, PostgreSQL. No home-made CMS that only we can get into |
|---|---|
| Code and access | Yours. The repository, the domain and the server are registered to you |
| Deployment | Documented and automated, so it does not live in our memory. Another developer will run it without talking to us |
| Backups | Daily, restorable from any day |
A website, servers,
a sales and warehouse
system.
If you already have your own infrastructure, or you need a hand getting started, you are in the right place.
In a large production environment at Medos we plugged an invoicing automation into the WAPRO system they use and adapted it to KSeF. Documents are generated twice as fast as before.
Book a conversationContract, payments,
rights to the code.
Do we sign a contract?
Yes, on every project. Scope, deadlines, response time and what happens when we stop working together belong on paper, not in something agreed over the phone.
How do payments work?
A deposit at the start and the rest on delivery, split into stages on bigger projects.
Who owns the code?
You do. We do not build the kind of dependency where only we can change anything, because that works against both sides.
What if I want to move to someone else?
We hand over the access, the code and the deployment documentation. No fuss and no holding your domain hostage. We would rather you stayed because you are happy.