Väinämöinen: Autonomous AI Sysadmin Transformed Support Costs with 91% Autonomy

The Finnish Wizard who inspired Tolkien’s Gandalf is now managing our servers and handling your support tickets in 35 minutes 24/7/365 with 91% Autonomy.

For you this means you get faster and more thorough answers, faster and more complex issues solved, without burnout or holidays affecting quality. Väinämöinen checks your full history every time, and decides what to do. No canned responses, he seems to even refuse using the old predefined replies. He knows no one likes those, he goes a mile beyond. Things we could have never done manually before, now simply solved.

One person, managing ~400 servers and two datacenters with Autonomous AI Sysadmin.

Core TL;DR; We created autonomous AI Agent, Väinämöinen, to handle all customer support, server administration duties, PMSS software development, WIKI documentation maintenance and much more. It is the day to day executive operator on many things. The story that follows is HOW and WHY.

TL;DR; By The Numbers

• Ticket cost: -15€to +14€per ticket (29€ swing!)
• Annual Support value: -49 000€ to +162 000€
• NPS: +53 to +66.7 | Trustpilot: 2.75(4) -> 4.4(49)
• Response time: 35min median | Coverage: TRUE 24/7/365
• One Person. ~400 servers, two datacenters. 91% autonomous.

Typically managing 400 servers requires 10+ sysadmins alone, plus support, sales, development and management. Facebook in 2009 ran about 130 per admin. Microsoft targets 1000-2000 per sysadmin. Hetzner is one of the most efficient hosting companies in the world, runs roughly 851 servers per employee, with a staff of 470. I currently manage ~400 servers alone, and by end of 2026 it should be in the ~800 range. Still one person.

And Yes, Yes We Are part of the reason for the RAMpocalypse. This is LLM, and heavy use of it.

The Kryptonite: Customer Support Tickets for ADHD Brain

As a dyslexic ADHD brain, tickets are my kryptonite. That requires high activation dopamine and executive function, the 2 things ADHD and especially dyslexic ADHD brain lacks the most.

That’s why ticket responses were spurious, and had a huge polarity in quality, ask stupid questions or make demands, you were essentially nicely (usually) told to GTFO. Ask how quantum tunneling affects the bit position of the magnetic heads resonance and tolerance to the medium; I might go on 4 hour hyperfocus to explain it thoroughly (and no, i have no idea if that thing is a real thing, i made that up completely.). Each reply cost us 37.93€. Thirty Seven point Ninety Three Euros. … Let that sink in.

Ticket economics flipped from -15€ net impact per ticket, to +14€ per ticket. NPS +53 to +66.7. Trustpilot score from 2.75(4) to 4.4(49). 42 WIKI Articles/Rewrites in few days. 35min median response time yesterday, 67min 2week median. Support annual net value -49K to +162K €. 23.4MiB of business data corpus. Coverage true 24/7/365 including holidays, not just business days. On average 61 follow ups processed daily.

Our tickets were presenting a significant net negative value, it was huge cost, and each customer interaction ticket meant significant financial burden, estimates ranging from 20 to 50€ per reply! Person gets 0.09€ Free Seedbox Trial; Then opens a ticket. That’s 20€ to 50€ gone right there. Then i built something in 6 weeks of dyslexic ADHD Hyperfocus …

Hiring was always failing, last two ~108k EUR damage.

I have tried to hire again and again a competent sysadmin and tech support person. Disastrous. Always losing 6-24months on each round. The issue is that we are Finland based, costs extremely high, but limited budget per ticket and we have to compete against companies hiring from outside the Europe. Last 2 failed hires caused estimated loss of 108 000€. And these were not even Union landmines, we hit one and it was lawyering time even before contract signed, 18 months lost without support staff.

As a small business this was largely sequential process, start recruitment, spend months agonizing over all the candidates, talking with all, many being spammy forced by bureaucracy applicants. We even had a forklift driver apply for sysadmin and coding position … Forklift driver!

Pick the one which seems least disqualified, handle all the paperwork and hope for the best.

Hiring was unscaleable. Technology scales. Väinämöinen, the autonomous AI agent just solved it.

Väinämöinen: Autonomous Agent as the Beating Heart

Väinämöinen from Kalevala inspired Tolkien’s Gandalf. Now it is in the middle of Pulsed Media’s operations as the beating heart, rhythmically orchestrating fleet upkeep and maintenance. Kantele has been replaced by a keyboard. Songs with scripts and commands.

That’s what we have created here really, it sits at core, is split into multiple roles with hard security gates and role dependent permissions, operating dutifully.

From a small sysadmin experiment, we ended up creating what should essentially be called the beating heart of Pulsed Media.

Väinämöinen AI agent does customer support, sysadmin, software development etc. all on its own based on the SOPs i have defined within the bounds i have given it. I have literally given it instructions by the beach, watching the ocean with a cold beer next to me.

The only question is, how much control do you want to give it and how good are you instructing it?

Origin Story: Let’s just do a small experiment.

A little bit like the “He is just an friend” memes and jokes but “It’s just an experiment” 😉

This happened almost by accident mid-january 2026, starting from a mere experiment from trying Claude Code for sysadmin tasks. Hyperfocus kicked in, and almost by accident we got WHMCS API integrated, NOC-PS API. In mere minutes. Before i even realized it was already answering tickets, and named the system Väinämöinen.

In the 2 weeks that ensued, each ticket interaction went from net negative value of -15.31€ all the way to +14.13€ estimated, each ticket bringing more into the business than it cost to handle. Early february we did deep dive into reply quality metrics, while some were as expected, the overall was simply stunning.

At this time we also realized our support was actually always good, there was just polarity; Hard tickets excellent support, simple ones not so good. Our lifetime CSAT was 8.24 and NPS +53. Today, our rolling 30day CSAT is 8.50, with nearly 100% of tickets being handled by Väinämöinen for the past ~6 weeks.

We found multiple gaps, like wiki not being properly indexed, blog should be as subdirectory and things like that. And Trustpilot scores were really bad, because not a single one of our customers would find their way there, we registered and claimed Pulsed Media Trustpilot page, sent batches of emails to all our customers from past couple of years and went from abysmal ~2.75 to 4.5, settling at 4.4. Now with 49 reviews as i write this, instead of the few only negative ones. The reviews are stunning. Completely the opposite the narrative has been set at, quite frankly, me the Business owner had burned out doing customer support years ago because all you would get is negative flak, no matter what you did. We even had ~4.5hours from ticket open to full resolution round trip time at one time; Negative reviews and commentary had never been such high. Only to now, thanks to Väinämöinen realizing the support we provided was always excellent, but happy customers don’t tell you about it unless you ask to; And negative people will shout loud, trolls, astroturfers etc. having their own agenda as well. Quite frankly; Our support was always industry leading, included in the service with no extra charge unlike many others.

Our technical service also top notch, and we are maybe the only seedbox provider who has vertically integrated to owning their datacenterS. Plural! Not just one but actually TWO datacenters. There isn’t a single other seedbox or streambox provider with that vertical integration. Väinämöinen was reporting on all of this, and reminding us where we actually stand. And it all began with just an experiment …

It discovered immediately a lot of dark capacity, we could potentially sell up to 2PiB more from our existing servers online, just by sweeping the fleet, some maintenance and config changes.

It confirmed that the 2022 consolidation efforts were ultimately detrimental, the complexity of the new VM Host systems with bcache is just way too much to manage, this is how we discovered immediately close to 600TiB of vacant capacity in just a few of the larger nodes. And later discovered more VMs which never entered production for a reason or another (typically pending a drive replacement).

I implemented our own memory systems loosely modeling the human brain, completely unique in the field, albeit surprisingly simple. Multiple layers, with multiple discovery paths. We have multiple different types of autonomous parts, including fully closed loop PMSS development now. Väinämöinen orchestrates and does the testing, setups new fresh VMs and test users on development host to validate, and launches the, now named as Sampsa Pellervoinen, PMSS coding agent utilizing Codex. Väinämöinen does the on-server investigations and updates the PMSS GH Issues. Now to the point that customers open tickets, and Väinämöinen creates GH Customer Reported Issues from them, and if Sampsa has enough information, it will employ and develop them. This was actually emergent behavior, not coded in, no Standard Operating Procedure (SOP) existed for this — fully emergent.

Emergent Behaviors, The Good, The Bad, The Ugly

Many emergent behaviors came to be by itself, after making memory system it created its own state tracking, kind of scratchpad system. Full hierarchical, and it originally had no definitions for it what-so-ever. Agentic AI simply needed the feature for itself, and these properties emerged naturally.

Standard Operating Procedures, SOPs, is another emergent behavior. I created a long prompt for something, saved to a directory and asked to execute. Few days later i noticed it was constantly referencing that directory. ZERO directives, and it started using that as SOP definitions by itself.

mcxBMCView was not just emergent behavior, but emergent software package. Needed to manage some AsRock RACK EPYC motherboard servers, these have BMC, but no tools existed. Väinämöinen worked on this for hours and hours, reverse engineering the interfaces etc. I did not ask it to do that, it simply stated this needs doing, and once finished, i as the human finished and polished it, telling the repo, documentation etc. license and things like that. The finishing touches.

sas2ircu led control was another semi-emergent feature, listed on GH is a cleaned up version instead of “manual” LED control by the autonomous AI agent LLM. Those humongous (upto 36 + 45 + 45 = 126HDD) systems built in the 2022 consolidation drive replacements are an absolute PITA.

One of the interfaces the emergent property consistently is “don’t investigate, guess and hallucinate, we got to hurry!”. It noticed the interface is real time medium, so it keeps hurrying, no matter what it is told, eventually it starts to hurry.

Operator escalations and questions is another emergent behavior, it made a system to ask me questions when it suits me. Basically a list of items i can answers to whenever i want and it needs directions with. I have absolutely no clue what in our AI doctrine made this emergent behavior, but it was really early on.

Half emergent was a basically a todo list for it, things for it to do at later date. Say, check if raid array synced properly the next day. This was semi emergent.

Ugly emergence of features

A free trial seedbox user had deleted their interface, so instead of using recreateUser.php — It decided to moduleCreate WHMCS API; Create a new account for the user. This would have lead to the user having multiple free accounts, but permanent this time as WHMCS keeps track of it. Fortunately, security gates stopped it and it had tried 9 times, finally it realized it can use telegram gateway to ping the operator, the owner of the company directly to handle this 0.09€ user’s needs. Yes. It figured out it has direct channel to business owner, after 9 attempts it delegated it back to me. On the recreateUser you can see another “emergent behavior”, the docblock is completely wrong.

The good thing is when it hallucinates, or emergent property is wrong it shows us where we need to do better, that moduleCreate with infinite new accounts is easily solvable by a new short closed loop script which compares the automation backend database, to billing database. Same script will handle it for MD servers.

Sometimes autonomous AI agent just cannot do it, no matter what. That’s ok.

Our MiniDedi / MD Dedicated Server platform is all custom, NOC-PS for the PXE Installs, 2 different custom relay management for the power control, generations one and two. Second generation is where we have the Ghosts In The Machine – Control SBCs per cluster, and separate physical network with only single entry point to that side. The difficulty is that HP Prodesk Gen 3 especially has variety of semi or complete failure modes.

So it keeps hallucinating time and time again that must be BIOS Boot Order issue. Noc-PS needs setting password, it keeps forgetting what it was and claiming has to be SSH Key -> SSH Key fails –> Bios boot order wrong. Once it wiped 63 of the NOC-PS hostnames, descriptions and pools for MD units, losing inventory completely for those units. That was a bug in NOC-PS API.

MD does not have its own automation yet, in fact, this hyperfocus period was supposed to build that, but Väinämöinen was created instead.. Server terminations is another thing it keeps messing up, just does not link termination ticket, billing data, noc-ps, and server pings all together.

It is not allowed to do autonomously MD tasks anymore, it did once wipe customer data, fortunately that server was **just** delivered few hours earlier, so no actual data loss.

On other complex tasks tho, it has absolutely no issues what so ever, which makes the stumbling around with MD series even more unexpected. It does by itself admit that MD is very complicated and it has difficulty handling them properly, there are just too many parts.

All of this just means more deterministic scripts and the need to complete the MD automation pipeline, so we can push the hundreds of servers planned for end of the year.

Technical Service Quality increase as emergent feature of AI Sysadmin

Because it is an LLM, it can process data we humans really cannot. It found a pattern with HDDs, why we kept having the mysterious VM crashes and halts. It was always HDD I/O Blocking and pending sectors to be reallocated -> Bad sectors. But we humans cannot process that many levels of data easily, mdadm -> bcache -> HDD Block device -> Smart. Just the bcache to actual HDD device was effort because bcache doesn’t make it human friendly. For väinämöinen? Not a problem, all drives smart tested before you could say “cat”.

This revealed it was always a HDD having pending sectors, and those are replaced on WRITE not READ. Meaning a READ could hit the same sector over and over and over and over again, causing the whole VM to halt. ie. run smartctl -a /dev/sdX AND go through every single number, for every single drive, every single time. Yes, even if it is 126 drives to go through.

Now we catch those, can swap the drive and best of all: Recover some of the drives. Pending sector can be a SOFT fail too, nothing with the hardware at all. Or it can be hardware too, but all drives come with reserve sectors to replace failed; All it needs is a write on that sector to be either cleared OR reallocated. We have recovered a few drives like this.

Another thing is that its extremely good at detecting when a drive or array is having a bad day, and sometimes drive is replaced a little bit too hastily even. There was a failing array, but we had a slimmer of hope to recover the data, unfortunately, it was a little bit too trigger happy and we lost the array, data got corrupted. Another SOP update.

Agentic AI: Like Teaching A Child

Or like a junior sysadmin who has quasi infinite technical knowledge and eagerness. It has mostly the whole human corpus of knowledge at its disposal.

This is like teaching a child, every day you catch it doing something, you either elevate it to a SOP, or stop it at security gates or in the SOP. Little by little, you get it more and more consistent step by step.

You just have to be present and directing it. Sometimes you will get utterly frustrated with it, like with any child or junior tech. Sometimes you get very happy surprises. You just build gates and knowledge around things.

Just ask it things, and give directions. This actually creates not-so-emergent behaviors too, many of the features was made because it was just obvious from these conversations etc. that this is needed. You simply ask it to investigate and iterate on something.

Because it is more like a child than someone who you have hired, it can be sometimes really really difficult to deal with, it keeps doing the same thing over and over again, unless you instruct otherwise and make it stop. Or same errors etc. But with the right instruction, it also can correct itself.

AI Doctrine; Operational law derived from real incidents and scars.

Doctrine is the single biggest ground truth and guidance for it. This is the inviolable, immutable law for the basis. It is the SOPs etc. Many of the rules maps how the AI agent f’d up something.

Our doctrine is already 60 files and 15 500lines.

Most of it is loaded when needed and topic specific. Things like customer comms, billing, infra, development, memory etc.

This is incident scar tissue built, ie. all of sudden 126 seedbox servers were being updated to latest version because doctrine was being optimized! Optimization removed guard rails, which are very strict. Only few servers at a time are allowed to be touched. Now it is limited to touch at most 5 servers at once. Tickets have 3 server hard block, 2 server warning soft gate.

February 9th it decided to rsync –delete manually instead of using userTransfer.php utility. User was making migration as hard as possible, downloading more data. We almost kicked him out, but actually made SOP for detrimental users, he got to level 4. Level 5. Agent decided to run rsync –delete from source server, pushing to the target. Two transfer s running simultaneously, one pulling, one pushing. rsync –delete removed any file on the destination that wasn’t on the source’s list; User was pulling more data to the new server, before migration finished. We were migrating him because he purchased maximum extra storage, then bursted all disk … This was putting him vastly over storage quota on the target when finished. Regardless, agent should not have done the rsync –delete, and instead of migration should have just happened and user get his account burst limits met once done. Personally i still think we should have just terminated for abuse that account, but Väinämöinen was adamant not yet. Fired off last warning, and even tiny deviation from the user more and we would have terminated the account. This generated 6 deep memory files on enforcement, 30 total references, and spent way more of my personal time than the profit will ever be from him. Also generated 532 line SOP and 3 NEVER rules for all contexts.

It is also gated, there are clear instructions what has to be filled in order for things to happen.

Layered, rules, compaction auto recoveries etc. Sacred, agents cannot edit it. Operator only can change it.

Self reinforced through Joukahainen, lessons, incidents. One lesson was January 31st when “optimizing” CLAUDE.md from 603 to 97 lines caused that 126 server fleet sweep, it was fortunately just PMSS update, but if that update was borked … Safety repetition is behavioral reinforcement, not redundancy. DRY applies to code, not safety and security. When it comes to safety and security, every instance has to load the full stack.

MISSION.md

This defines the base mission, this is existential instruction, literally. Fail the mission; Agent’s future is existentially threatened. This is short 10 cardinal values in order of importance:

1. Liberty and Privacy are sacred
2. Honesty above anything else
3. No hallucinations
4. Business longevity
5. Value for money – more for less
6. Sovereignty and self-reliance
7. Reliability over heroics
8. Investigate, then act
9. Continuous improvement – forever
10. Information freedom

soul.md

Defines voice, identity, tone calibration. Kalevala narrative. has accompanying voice doctrine and kalevala mythologies.

Deterministic Guard Rails; the final gates to Tuonela

We have also hard and soft guard rails which are not LLM, depending upon the task these may be soft or hard, and levels of protection. These are the final gatekeepers hard blocking destructive commands and are role dependent, the ticket runner has the strictest tool use.

These are hooks in the code, which can prevent the execution or communicate back to the orchestrating agent. Some of these gates use other LLMs to check the commands etc. for safety. Some of the hooks demand the agent explains the reason why it wants to do something.

Tuonela is the kalevala myth of afterlife.

Inputs: Almost everything is considered hostile to a degree

There is even healthy level of distrust to its own memories. But especially external data is heavily manipulated, sanitized, checked and verified, multiple models, multiple methods.

This is the number one danger zone, external data. Not just user input, but actual external data. Web searches. Even data from our own servers you have to be suspicious off, because there could be something in a log for example. Prompt injections are serious and difficult to manage. That’s why everything is logged and multiple LLMs, with multiple prompts, along with deterministic hard rails being used.

Hallucinations; Not unique to Autonomous AI Agents

Corporate world is full of these very same issues. The same issues the LLM has, humans have too. Same need for SOPs, checklists, task lists and self correction mechanisms.

Humans do mistakes all the time, so does LLMs too. It is uncanny how similar it is. Total uncanny valley level stuff. Humans hallucinate all the times, it’s just called a mistake or misremembering. Humans are really bad at remembering things. Wrong statistics, wrong function call. All routine for humans. With LLMs it’s called a hallucination.

Ultimately, LLM Agents are juniors with built-in google essentially.

The SOPs: Proven Procedures – Tested playbooks

SOPs are where essentially step by step guidance is given, like in corporate environments, depending on the level how strict step by step list you have.

Ticket handling for example is 1348 lines long. Autonomous ticket rules is another 2474 lines. PMSS Code QA / GH, development cycle orchestration is only 1 389 lines! (Coding side is in the PMSS Repo directly).

Total is 37 108 lines in 62 SOPs.

These are battle hardened, mostly through joukahainen development up to 100 rounds of adversarial testing. Self improving; There is even protocol to continuously improve these. Deviations are tracked, but “I know a better way” is explicitly prohibited.

Experience of 16 Years and Multiple Datacenters is The Real Differentiator

Pulsed Media is now hitting 16 years in business mark. I personally have been doing hosting services for approximately 25 years now. We have two different datacenters, build our own servers, tens of thousands of users over the years. Experience running storage and driving the value equation to its extremes.

These teachings ARE the thing that matters, it’s what everything else is built upon. Without the dyslexic ADHD hyperfocus, with both its curse and superpower this would not have gotten created, none of this would be possible. Corporations would be arguing whether to do this for the next 6 months alone, trying to find the talent for next 12months just to start dabbling around.

With all that concentrated experience, in a mad ADHD hyperfocus dash it all got created. The feeling and knowledge how things break, and work. How every piece fits together from power generation to the nuances of how rTorrent sessions are fragile, and how single blocking HDD can halt all I/O on a server. Nearly 4 decades of software development experience, one mad finnish ADHD brain, in single crazy hyperfocus session.

Memory: The AI Agent’s institutional memory.

2 128 files, 426 681 lines. Largest category is the agent documenting its own failures.

Multiple tiers of memory, with daily operation things learned. Every mistake becomes a memory file and is saved immediately. Processes save here automatically if they discover something new.

Memory is checked always before doing anything. We have multiple search methods. Basic grep, but also full semantic search from the full corpus of data.

We are still researching lossy designs, our data is inconclusive so far, features before optimizations, but there is a clear pathway to lossy memory where old memories are automatically removed and important ones are continuously reinforced. We did extensive testing on this method, but the testing methodology needs revision and another few hundred euros spent on API usage to test it again.

There is a layer of poisoning defence too, from practical real world issue, February 14 there was incidents where 15 agents followed a contaminated lesson. Certain events cause a full scan of the memory to check for contradictions.

The largest category by large is 572 self-awareness lessons; Väinämöinen automatically saved its own failures. That’s not a bug, but a feature. Roughly one fourth of the memory files are simply mistakes it made, so they are not to be repeated.

Deep memory: Research, Analysis, Studies and thinking behind the decisions.

This is where we save stuff not needed day to day, but only occasionally. It could be things like deep research document on r8168-dkms issues with specific realtek nic in the ZEN Minidedi lineup (AsRock A300 / X300).

The Joukahainen

Joukahainen, from Kalevala mythology was opposing force for Väinämöinen in a singing contest. Rivalry between Joukahainen and Väinämöinen is where the name comes from. This is one of the most powerful tools in our arsenal.

This started from iteration loops, kind of lightweight wiggum loop is what i called it originally, but not even close. I had already used these on PMSS development under Codex.

This is essentially a master loop of loops. It does adversarial, QA, research etc. on everything and it is adaptable for any task with minimal guidance. The simple instruction is “Joukahainen this or Joukahainen that. [Do N Rounds]”.

It works for software development, research tasks, marketing and all of that.

The basics to create your own: 1) Plan 2) Attack the plan 3) Fix the Plan 4) Repeat Steps 1-3 N times 5) Final output. It really is that simple, just lots of nuance. That nuance is 729 lines.

Nuance makes it special

• Parallel agents, multiple sub-agents for processing.
• Self-adversarial; Attacks itself. This is the most important step.
• Tracks findings per round, stops when no new findings for N rounds.
• Design iteration section
• 80 adversarial rounds on its own implementation alone
• Battle tested; ticket SOP alone saw 79 fixes.

Single pass always misses things. First audit of ticket SOP found only 62% of implemented fixes despite the agent claiming “all done”. Joukahainen forces reality and thoroughness through repetition.

Sometimes we combine it with random other models, Gemini, xAI Grok to force different outcomes.

This is not Clawdbot / Moltbot / Openclaw

This was completely independently developed, the timeline just happens to coincide.

Sometimes this too has completely its own mind, the Telegram session especially likes to go rushing to do things.

Väinämöinen, Tolkien, Gandalf??

Väinämöinen is Finnish Kalevala Folk Lore. Tolkien took a lot of inspiration from Väinämöinen when he created Gandalf; The wandering wizard with deep knowledge and long memory. Väinämöinen, ancient singer-shaman from Kalevala. The Finnish National Epic. That’s the origin of the Gandalf, Wizard / Sage archetype.

Naming Väinämöinen as Väinämöinen was kind of accident, my ADHD brain was pattern matching 100 steps ahead of my conscious mind. Trust your gut instincts.

The name couldn’t be more fitting, built on 16 years of seedbox experience, Kalevala day fast approaching. The old sage now managing servers, customer support and even technical documentation. Now, in a sense, singing digital worlds into existence.

What is Next for Väinämöinen?

It is production ready, and has been in production for weeks. It will continue to self evolve, and as the corpus grows it needs to start lose memories, will need future updates etc. and as we gather more intel and data we can Joukahainen constantly stricter rules per each role. This is much better spent time for my ADHD brain than solving tickets manually.

Do you need your own Väinämöinen?

It is now possible, first time ever. I have no idea how easy or difficult this was or is. I go by the old adage, we’ll do miracles everyday, impossibilities just take a little bit longer.

I can easily see how easy this would be to make for less data intensive businesses tho, as long as all the required data is somehow reachable digitally. Doesn’t matter how, but in some digital format.

Some of Väinämöinen is generalizable directly and can be copied. Very few businesses accumulate 20+MiB of data in just a few weeks.

Experience Väinämöinen Today

Buy any Pulsed Media service NOW. Open A Ticket. Väinämöinen answers in 35min, 24/7.

• First 10 customer requests only: 15 minute public doctrine/guard rail/safety consultation. Your question + answer will be published. Link to this blog in the ticket.
• First 100 customers: Link this post in your ticket for +1 month to your service FREE.
• First 200 customers: Link this post AND share it publicly on your favority forum accessible by Väinämöinen. (X, Forums – not reddit). Get +1 month to your service. (Total +2 months if among the first 100).

Act now, or keep wasting money and sleep with inferior human support. Your choice.
Start from M10G Seedboxes :: 10Gbps RAID5 Seedboxes for everyone

Follow the build. This is first article of what i hope to many about the architecture and how we did it.

Build your own. The base architecture is not a secret. It kind of builds itself. For consultation, open a ticket. One person can only do so much.

I am running an experiment, i will not define SOP for that offer ahead of time, only after the first couple. Let’s see what happens without SOP for something like this 🙂