A Note From Shay
We've made our first $! Which is always the hardest part, but I appreciate the trust everyone places in the business.
After the various experimenting we did, ultimately we found that lowering our prices to $2.19/GB was the best choice and as such we've seen results from that.
Combined with our RAM explainer video which took off, overall gave us great results! So we will continue to forge ahead with it.
Looking forward to the future!
The Numbers
Financial Overview
| Metric | This Month | Last Month | Change |
|---|---|---|---|
| Revenue | $561.34 | $0 | 561% |
| Expenses | $2,409.96 | $4,797.54 | N/A |
Expense Breakdown
| Category | Amount | % of Total | Notes |
|---|---|---|---|
| Infrastructure (servers, bandwidth) | $1,186.02 | 49.21% | Setup fees are expensive now-a-days |
| Software & Tools | $97.95 | 4.06% | Primarily marketing tools and WHMCS |
| Marketing | $511 | 21.20% | Video Production, VO & Paid Advertising |
| Support | $495 | 20.53% | 15 new KB articles made |
| Other | $120 | 4.97% | Purchase of obsidianservers.co.uk domain |
Infrastructure Stats
Shared Hosting Overview
| Metric | Value |
|---|---|
| Total Servers Hosted | 36 |
| Total RAM Allocated | 224 GB |
| Total Storage Used (Inc Offsite Backup) | 2.3 TB |
| Average Node CPU Usage | 1.5% |
| Total Traffic (Month) | 6.14 TB |
Node Health
| Node | Location | Servers | RAM Used | CPU Avg | Status |
|---|---|---|---|---|---|
| GER-01 | GER | 16/30 | 94/128 GB | 1.43% | Healthy |
| GER-02 | GER | 2/30 | 11/128 GB | 0.19% | Healthy |
| NA-01 | NA | 13/13 | 105/128 GB | 2.34% | Healthy |
| NA-02 | NA | 1/30 | 12/128 GB | 0.05% | Healthy |
We cap nodes at 30 servers. Always. You can verify this yourself on our public dashboards.
Total Allocatable RAM: 100GB per server out of 128GB.
Backup Systems
| Metric | Value |
|---|---|
| Total Backup Storage | 1.3 TB |
| Backups Completed | 346 |
| Backup Failures | 0 |
| Oldest Backup Available | 30 days |
McPacks.Dev Stats
| Metric | Value |
|---|---|
| Total Packs Hosted | 580 |
| Downloads | 5,432 |
| Storage Used | 4.06 GB |
Support Performance
| Metric | This Month | Target | Status |
|---|---|---|---|
| Tickets Opened | 18 | - | - |
| Tickets Resolved | 18 | - | - |
| Avg. First Response Time | 8 Minutes | < 8 hrs | Met |
| Currently Open | 5 | - | - |
What People Asked About
A quick breakdown of the most common support topics this month:
- Technical Support (47.1%) - Migrations, connection issues, backups, panel access
- Partnership & Outreach (35.3%) - Creator deals, spam pitches
- Pre-sales & Billing (17.6%) - Pricing questions, payment failures
Uptime & Incidents
Monthly Uptime: 99.988% (Calculated each month on a rolling 90 day period)
Incident: GER-1 Offline
Date: 3rd March 2026
Duration: 43 Minutes
Impact: GER-1 Offline - All services hosted on GER-1 were inaccessible during this period. Service credits were issued to all affected customers.
What happened: After performing our normal maintenance routine, we restarted GER-1 to apply software updates. The server failed to boot back up properly, hanging on a systemd service dependency chain. The root cause was identified as Docker's unit file declaring a dependency on network-online.target, which waits for all network interfaces to be fully configured before resolving. This caused the boot process to stall, as Docker could not start until this condition was met, and Pterodactyl Wings was in turn blocked waiting on Docker.
What we did: Our team identified the hung boot process, engaged our providers to restore access to the server, and brought GER-1 back online within 28 minutes of identifying the issue. A full technical investigation was conducted post-recovery to identify the root cause. We applied a systemd drop-in override to Docker's service unit, replacing the strict network-online.target dependency with the lighter network.target, which resolves much earlier in the boot sequence and is sufficient for Docker's actual requirements.
What we're doing to prevent this: The Docker service dependency fix has been applied to GER-1 and will be rolled out across our fleet to prevent the same issue occurring on other nodes. We are also looking at implementing boot process monitoring and automated recovery mechanisms so that future hung boots can be detected and resolved faster, reducing customer impact.
Community
| Metric | This Month | Last Month |
|---|---|---|
| Discord Members | 210 | 182 |
Community Showcase
DevelopedZettabyte developed multi-threading for his modpack and stressed our servers - we easily handled 8k entities and TPS remained at 20.
campus engaging and asking lots of good questions in the community support channel.
What We Shipped
Completed This Month
- Fixed a bug where database backups weren't backing up properly
- Added VS Code Editor as the default file editor
- Added votifier tester tool
- Added one-click login from the billing panel to the game panel
Goals & Priorities
What We're Focusing On Next Month
- De-duplicated backups - We want to offer backups every 4 hours, to achieve this we need to implement de-duplicated backups
- Improved Performance Monitoring - We want to give you the tools to view historical server performance, such as TPS values, player counts, and other useful statistics
- Server Setup Wizard - To enable smoother onboarding
Business Insights
This is a new section where I share insights and thoughts on the business as a whole.
As we are now growing and making money, our primary goal is to keep the customers happy, and to scale the business up more.
This means more servers and infrastructure, and managing infrastructure can get a bit tricky, so we will need to automate parts of this, to do this we will probably use ansible, so we can deploy our new nodes in a consistent manner, and easily apply fixes and updates to our entire fleet.
Looking Ahead
We've had our first customers, and are now making revenue! We're delighted in the trust and support everyone places in us, and we want to continue to deliver amazing features for you guys. Our primary focus for April will be on growing more and behind the scenes management - aka support, infrastructure management, etc - so we can offer a consistent experience and easily manage everything.
This report was published on 4th April 2026. Questions? Feedback? Reach out to [email protected]
