Your own server instead of subscriptions
I build open-source tools on your own server - CRM, automations, a knowledge base, a blog - so your data stays with you and your monthly bills go down.
Your data stays with you
I don't make you choose between someone else's cloud and no tool at all. I deploy open-source software on your own server, so export and backup are always in your hands.
The bill shrinks with every new tool
One server runs many applications at once. Instead of five SaaS subscriptions, you pay for one VPS and its administration.
I know both sides
I'm migrating my own CRM from HubSpot to self-hosting right now, so I know when SaaS is the faster start and when your own server pays off at scale.
A clear agreement from day one
We sign an SLA and a data processing agreement before I deploy anything, because hosting also means responsibility for uptime, backup, and data protection.
Where we start depends on what you have today
You don't have any of these tools yet.
Then we start with a conversation about what hurts the most today - CRM, automations between systems, a knowledge base, or a blog - and pick one tool to start with, instead of deploying everything at once.
You already use SaaS and want to move to your own server.
Then we start with an inventory of the data in your current tool and a migration plan with no downtime - export, import, a parallel period, and only then switching off the old subscription.
What the work covers
- [ 1 ]
Choosing the stack
Plane, n8n, Kimai, Twenty, Ghost, or another open-source tool, matched to what you're paying a subscription to solve today.
- [ 2 ]
Deployment on a VPS
Installation, configuration, integration with what you already use (mail, CRM, your website).
- [ 3 ]
Data migration
Moving from your current SaaS tool, if you have one, without losing history.
- [ 4 ]
SLA and a data processing agreement
A clear agreement: what I guarantee (uptime, backup), what's your responsibility, how personal data protection works.
- [ 5 ]
Ongoing administration
Updates, backups, monitoring - as part of a retainer.
What I don't do
- Online stores and infrastructure for heavy traffic. I build tools for a single company, not platforms for thousands of concurrent users.
- Migrations without a data processing agreement. If a tool processes personal data, a DPA is a requirement, not an option.
- Background maintenance without an agreed SLA. I only take responsibility for uptime and backups where it's written down.
How you will know it works
We start by recording how much you're paying today for the subscriptions this tool will replace, and what state the data is in (how many records, how big an export). After deployment we compare the monthly bill before and after, and confirm the data with a screenshot from the new tool - so you see not just the savings, but that nothing got lost along the way.
What I can't show you yet
I won't show you my own migration from a subscription to my own server yet - I'm migrating my own CRM from HubSpot to my own server right now, and I don't have a finished result to show. When it's done, I'll add it here as proof - not at a client's, but my own.
I also have a fresh commercial deployment on a dedicated server - a full ecosystem, not just a website - that I can't name the client for yet. When I can, it'll join here as a second proof point.
What I show above are client projects: Smaczaki and Warwick Legal Network went live on their own server from day one, not as the result of a migration. I'd rather say plainly what's still in progress than blur the line between what's done and what's happening right now.
How it looks in practice
As of August 2026 Smaczaki: a wholesale website for an importer of dog treats
eight pages with a catalog of more than a hundred items, running as a static site on my server, with no database and no software fees. A month passed from order confirmation to launch, and the day after the site opened to search engines its home page was already in the Google index.
See the case study
As of August 2026 Warwick Legal Network: AI avatar videos and an ebook for law firms
Two educational videos, an ebook with a ready-made matrix of prompts and a page holding all the materials, prepared for the Dubai conference of this international network of law firms. I ran the whole production myself, with no studio and no film crew.
See the case study
What it costs
I bill deployment as a one-off, and I quote the amount after we talk about which tool we're choosing and how much data it needs to carry. Hosting and administration are billed as a fixed monthly fee: from 20-50 zł/month for a simple static site, through a flat rate per period for a campaign landing page, up to an individual quote for a full application stack - depending on how many resources it needs.
Frequently asked questions
Will I lose access to my data if I stop working with you?
No. Your data lives on your own server from day one, so exporting and continuing to use it doesn't depend on whether we keep working together.
How is this different from regular hosting?
Regular hosting gives you space for files. I choose, deploy, and maintain a specific tool - a CRM, an automation, a knowledge base - ready to work, not a raw server.
What happens if the server goes down?
The SLA sets out how fast I respond and how often I back up - we agree on that before we start, not after an outage.
Can I start with one tool and add more later?
Yes, that's the natural way to work - one server runs many applications, so each additional tool costs marginally less than the first.
Let's see which of your subscriptions can be replaced
Write and tell me which paid tools you're using today. I'll get back to you with which ones are worth moving to your own server, and which are better left alone.