SILOTEK
Sheet 03 · RootOpsFacility 03 · Sealed
Facility 03 · RootOps

Custom systems,engineered to spec.

RootOps is the SiloTek engineering bench. When an off-the-shelf resource will not cut it, we scope, build, deploy and maintain the scripts, bots, APIs and automation that run your operation — the same stack that powers OmniPanel and SiloTek Hosting.

ROOTOPS — bench status
 
[ OK ] shipped builds — maintained
[ OK ] support — active for clients
[ WAIT ] new scopes — queue closed
[ WAIT ] bench — at capacity
 
reopening — announced in Discord
 
rootops:~$
SILOTEK · CRT-03
Otto, the SiloTek engineer

Fig. 1 — Engineering bench, std. issue

Scoped per build·Fixed quote·Source + docs·150+ players testedQueue closed
Bench status
Sealed
Quote
Fixed
Handover
Source + docs
Contact
Discord
Otto raising a hand: stop
Notice 03 · Bench closed

Not taking new scopes right now.

RootOps is sealed while the bench is at capacity. Builds already shipped stay supported and existing clients are unaffected — this only means we are not opening new projects until the queue clears. The spec below stays published so you know exactly what to expect when it reopens.

§ 03.A

Existing builds unaffected

Everything already shipped stays supported and patched.

§ 03.B

Waitlist, not a queue in the dark

Ask on Discord and you hear from us when the bench opens.

§ 03.C

Rather not wait?

OmniPanel and Hosting are open and running normally.

01

What the bench builds

6 kinds of work

From a single script to a whole platform. Every build is yours — source, documentation and a clean handover, or an ongoing maintenance arrangement if you would rather we keep it running.

§ 03.01

Scripts & mods

Resources built to your framework — jobs, economies, mechanics and UI, clean and performant at 150+ players.

§ 03.02

Discord bots

Tickets, moderation, verification and community recognition, wired into your server and billing where it matters.

§ 03.03

Private APIs

Internal HTTP APIs and webhooks that connect your game server, website, panel and Discord into one stack.

§ 03.04

Automation

Backups, deploys, sync jobs and scheduled tasks — the plumbing that keeps a live operation running unattended.

§ 03.05

Licensed delivery

Ship your product to other communities with license keys and protected cloud delivery, metered and revocable.

§ 03.06

Integrations

Stripe, Clerk, MySQL and the rest — glued together so data flows without manual work.

02

Scoped, shipped, supported

Fixed quote before code

Four stages, and you know the price before the first line is written. No open-ended hourly drift.

01

Scope

We map exactly what you need, the framework it must fit and the constraints — performance, budget and timeline — before a line of code is written. You get a fixed quote.

02

Build

Development happens against your real environment with staged previews, so you see progress and can course-correct instead of waiting for a big-bang delivery.

03

Deploy

We ship to your server or ours, wire up the integrations and hand over source and docs — with license keys and protected delivery if you are reselling.

04

Maintain

Optional ongoing support keeps everything patched and running, with monitoring and backups handled the same way we run our own production stack.

03

Real plumbing, not glue

Fig. 2 — deploy log

A private API endpoint issuing a license and a bot picking it up — the kind of internal wiring RootOps ships.

rootops — deploy log
 
$ curl -s https://api.silotek.dev/v1/licenses \
-H "authorization: Bearer ****" -d '{"product":"badlands-jobs"}'
{ "key": "SILO-7F3A-…-9C2D", "seats": 1, "status": "active" }
 
# bot picks it up and provisions the buyer
[bot] license SILO-7F3A issued → guild DustGrave
[bot] role @customer granted · channel #delivery posted
[api] webhook stripe.paid → license.activate 200 OK
[ ok ] delivery complete in 1.2s
SILOTEK · CRT-03
Form 03-R · RequisitionSilotek · Always running.
When it reopens

Get in line early.

The bench reopens when the queue clears, and it is announced in Discord first. Tell us what you are planning now and you are on the list — with a rough scope already discussed, so nothing starts from zero.

Otto giving a thumbs up next to a checklist