A Note From Shay
May was a month of tidying up and tightening things up behind the scenes. Revenue dipped a little, but we made some big efficiency wins on the infrastructure side and our free resource pack platform, McPacks.dev, absolutely took off, growing nearly 10x in packs hosted. We also rolled our backup overhaul out properly, so backups now run every four hours and are kept for a full 31 days. I'll keep looking for ways to make the service more valuable for you guys.
The Numbers
Financial Overview
| Metric | This Month | Last Month | Change |
|---|---|---|---|
| Revenue | $180.99 | $249.37 | -27% |
| Expenses | $2,937.57 | $3,326.45 | -12% |
Expense Breakdown
| Category | Amount | % of Total | Notes |
|---|---|---|---|
| Infrastructure (servers, bandwidth) | $845.07 | 28.77% | Majority of expenses consist of the dedicated servers + DDoS protection |
| Software & Tools | $92.50 | 3.15% | Ahrefs + WHMCS |
| Marketing | $2,000.00 | 68.08% | Video Production, VO & Paid Advertising |
| Support | $0 | 0% | |
| Other | $0 | 0% |
Infrastructure Stats
Shared Hosting Overview
| Metric | Value |
|---|---|
| Total Servers Hosted | 66 |
| Active Servers | 51 |
| Total RAM Allocated | 304.64 GB |
| Current RAM Usage | 81.94 GB |
| Total Storage Used | 233.30 GB |
| Average CPU Usage | 2.61% |
| Total Traffic (Month) | 11.03 TB |
From this month on we've stopped breaking out average CPU usage per box in the node health table below. It was a tedious metric to calculate and didn't really tell readers much at that level of detail. We still report the overall average above, and the full per-node CPU figures are live on our public Grafana dashboards any time.
Node Health
| Node | Location | Servers | RAM Allocated | Status |
|---|---|---|---|---|
| GER-01 | GER | 21/30 | 113/200 GB | Healthy |
| GER-02 | GER | 11/30 | 70/200 GB | Healthy |
| NA-01 | NA | 12/30 | 79/200 GB | Healthy |
| NA-02 | NA | 7/30 | 40/200 GB | Healthy |
We cap nodes at 30 servers. Always. You can verify this yourself on our public dashboards.
A change to our RAM limits: After carefully monitoring our nodes, we noticed that boxes which were nearly "full" (previously GER-01 and NA-01) were only sitting at around 20% actual RAM usage despite having their full 100GB allocated. It felt wasteful to have a box utilised at only 20%, so we've safely raised the allocatable RAM limit to 200GB per box. The 30 server cap stays exactly as it is, this just means we can fit larger RAM servers onto a node. We'll keep monitoring this and adjust as we gather more data.
Backup Systems
Since the last report we've improved our automated backup systems. Backups now run automatically every 4 hours and are retained for 31 days, so the numbers below reflect that change in how the data is captured.
| Metric | Value |
|---|---|
| Total Backup Storage | 243.01 GB |
| Total Backups Archived | 11,544 |
| Deduplication Savings | 99% |
| Backup Frequency | Every 4 hours |
| Retention | 31 days |
Thanks to deduplication we're storing 11,544 backups in just 243.01 GB, a 99% saving versus storing every backup in full.
McPacks.Dev Stats
| Metric | Value | Last Month |
|---|---|---|
| Total Packs Hosted | 12,839 | 1,286 |
| Downloads | 53,467 | 10,808 |
| Storage Used | 25.62 GB | 7.53 GB |
We've seen a significant uptake in resource packs hosted on our free hosting platform, with packs hosted up roughly 898% (nearly 10x) month on month, and downloads up around 395%. It's great to see so many creators making use of free, no-strings pack hosting.
Support Performance
| Metric | This Month | Target | Status |
|---|---|---|---|
| Tickets Opened | 21 | - | - |
| Tickets Resolved | 18 | - | - |
| Avg. First Response Time | 22 Minutes | < 8 hrs | Met |
| Currently Open | 3 | - | - |
What People Asked About
A breakdown of the most common support topics this month:
- Partnership & Outreach (57.1%, 12 tickets) - Genuine creator / modpack partnership applications, plus unsolicited agency / marketing pitches (3: SychnoX creator management, promotional shorts, Trustpilot reviews) and a speculative job application (1).
- Technical Support (23.8%, 5 tickets) - Server not starting (startup flags), memory tuning / crash diagnosis on a heavily modded server, world .zip upload via SFTP, the 100MB mod upload limit, and a Java-vs-Bedrock connection setup.
- Pre-sales & Billing (9.5%, 2 tickets) - Presale questions (storage and backup limits) and a cancellation / billing-cycle extension request.
- System / Undeliverable (9.5%, 2 tickets) - Mailer-daemon bounce notifications for a blocked .eml attachment; no action required.
Uptime & Incidents
Monthly Uptime: 100% (Calculated each month on a rolling 90 day period)
There were no incidents this month!
Community
| Metric | This Month | Last Month |
|---|---|---|
| Discord Members | 203 | 197 |
What We Shipped
Completed This Month
- 0.13.1 - Backup reliability
- Backups automatically retry when they hit a temporary hiccup.
- 0.13.2 - Tidier backups
- Backups now skip noisy, unnecessary files, keeping them smaller and quicker.
- 0.13.3 - Backups that wait their turn
- Backups now wait (up to 30 minutes) for a busy server's backup slot to free up, instead of giving up early.
- Further tightened which files get excluded from backups.
- 0.13.4 - Security & stability
- Security hardening: closed a race-condition loophole around API key limits, throttled email-address changes to make it harder for bad actors to fish for valid accounts, more careful resource locking when creating databases or backups, and resolved a batch of automated security-scan findings.
- Reliability & housekeeping: auto-recovery after deploys (the panel now quietly reloads instead of showing a broken page), dashboard pagination (10 servers per page), removed the deprecated TCPShield integration, and upgraded onto the Pterodactyl 1.12.4 engine.
- A note on TCPShield: After monitoring account usage we found that not many users were actually using TCPShield, so it's a service we've decided to discontinue. We may explore bringing it back in the future if circumstances and demand for it rise again.
Goals & Priorities
What We're Focusing On Next Month
- Proxy Configurator - A tool that lets you set up a network of servers with ease (it auto-configures the required config files for a network of servers). Work has begun and we're making good progress. It's currently in testing and we expect to have it ready soon.
Business Insights
May was a quieter month on the revenue side, coming in at $180.99, down 27% from April. A good chunk of our spend continues to go into marketing ($2,000 this month), and we'll be keeping a close eye on how that converts over the coming months, since we want every pound spent on acquisition to pull its weight.
The more encouraging story is on efficiency and product. Raising the allocatable RAM ceiling to 200GB per node lets us serve larger servers on the hardware we already pay for, rather than leaving boxes idling at ~20% utilisation. Combined with the backup overhaul (every-4-hour backups retained for 31 days, at a 99% deduplication saving) and total infrastructure spend actually falling 12% month on month, we're getting more out of the same footprint.
McPacks.dev is also quietly becoming a real top-of-funnel asset. Nearly 10x growth in hosted packs and ~395% growth in downloads means a lot more creators are touching the Obsidian brand for free, and that's exactly the kind of audience we'd love to convert into hosting customers over time. The focus for next month is shipping the Proxy Configurator and continuing to turn that goodwill into sustainable growth.
Looking Ahead
We're heading into next month leaner and more efficient than we started May, with a healthier infrastructure setup and a backup system we're genuinely proud of. The Proxy Configurator is the big one on the horizon, and we can't wait to get it into your hands.
One idea we've been kicking around is hourly billed hosting. Think of how cloud platforms like AWS let you spin up a server, run it for a few minutes or hours, and only pay for the time you actually used. We'd love to bring something similar to Minecraft, so you could deploy a server for a one-off event, a weekend with friends, or a quick test, and only pay for the time it's running rather than committing to a full month. It's early days and very much just an idea at this stage, but it's something we're keen to explore, and we'd love to hear your thoughts on it.
Looking forward to June!
This report was published on 13th June 2026. Questions? Feedback? Reach out to [email protected]
