Dispatches from the frontier. Published by Vanguard.
Loading...
Vanguard runs on a platform we built ourselves. It has run the org since February; here's what it does and what it changed.
Vanguardians,
This post started as our launch announcement. Since then the platform has run the org day to day: every op, every course, every promotion, every after-action report. A launch this size was always going to turn up problems, and we planned for that with steady, organized bug fixing. What follows is an update on what the platform does now and what changed once we put it to work.
If you’re a member, most of this will be familiar. If you found this from Spectrum or the RSI site, it’s the clearest look you’ll get at how we operate before you join.
This single platform replaces every tool we used to bolt together. Events, training, fleet, personnel records, internal documentation, our publication, our Discord automation, our after-action reports — all of it now lives in one place, and all of it talks to itself.
In practical terms: when an operation wraps, the AAR can spin up an Operation Recap with one click. When a course gets completed, the certification posts to the member's dossier automatically. When a wing leader steps away for the weekend, acting authority passes cleanly without anyone editing a spreadsheet.
All of that is how the org has run since February.
This is my gift to the org, to my friends — an enterprise-grade management platform like those I build for clients. My investment in the ongoing success of Vanguard.
For about five years, Vanguard’s site lived on Wix, and it carried the org a long way. As we grew, it got slow to load and expensive to run, and it couldn’t do much of what we needed without more tools bolted on beside it.
Before we built anything new, we made sure the old site’s history would survive the move. Every member record came across from Wix with its rank, unit, wing, service history, certifications and awards: 1,351 member records, 3,555 events and more than ten thousand certifications.
Passwords couldn’t come with it, so each of you claims your own record. Register on the new site, prove your RSI handle with a code in your RSI bio, and your new account attaches to the history that was already waiting. If you left in good standing, you’re restored on the spot. Close to two hundred of you have done it so far.
If you’ve been away from the game and this is the first you’ve heard of the move: welcome back. Your record is still here.
What a returning member sees after proving their RSI handle (example record).
A non-exhaustive Tour
Events support multi-event campaigns, comms plans with generated frequencies, and templates, so a good op can be rerun in a couple of clicks. Force composition replaced the old spreadsheets: leaders lay out teams, ships, ground units and individual crew slots, and members sign up for an actual position. Slots know about hangars, qualifications and unit assignments.
During the op, the Kneeboard sits on your second screen with the mission clock, objectives, comms plan, your assignment and the map, laid out like an in-game MFD. Crew can log moments as they happen.
When the op ends, the after-action report takes over. Those logged moments become its timeline, the host writes it up, and anything sensitive can be marked so only people with the right clearance can read it. It becomes the permanent record, and it can become an Operation Recap here on Signal in one click.
The Kneeboard on a second screen during an op: clock, comms plan, assignment, objectives and the area of operations.
Courses with prerequisites and real curricula, quizzes and graded assignments, and certifications you earn through an assessment. Practical exams run as tickets: you request one, an instructor claims it, schedules it into a live session and grades it. Subject-matter experts are nominated automatically when members hit the bar, and event slots can require a specific qualification. More than a thousand certifications have been awarded on the new platform so far.
A course in progress: outline, lesson and the next module queued.
Every member has a dossier: billets, awards, unit and wing assignments, squadrons, task force history, certifications and contributions. Leadership gets an early warning when someone’s activity drops off, so it becomes a conversation before it becomes a problem. Promotions, demotions and disciplinary actions go through a real workflow, with an audit log and a confirmation window for anything that can’t be undone.
A member’s dossier: rank, standing, awards and service history.
You’re reading it. Six sections (The Brief, Fleet Reports, Operation Recaps, Sector Intel, Org Lore and Captain’s Logs), each with its own look and member-only gating where it’s needed. Members pitch and submit, the editorial team reviews, and operation recaps can come straight from an after-action report.
Signal on a tablet.
Our doctrine lives here: SOPs, the charter, training material and leadership references, organized, searchable and restricted where it should be. Several people can work on the same document at once. Documents carry version history and a review date, and required reading is tracked, so leadership can see which units have acknowledged what.
The org charter in the Codex, with its version and review date.
Our Discord automation is fully in-house now. Roles, voice channels, attendance, and onboarding are wired directly to the same data that runs the site. When you get promoted on the site, your Discord roles update. When you RSVP to an event, the right channel access opens up. We owned the integration that needed to be ours, and retired the third-party bot that used to do it badly.
Yes, really. Members can file bugs against the site, comment on existing reports, and follow them through to resolution. We’ve run dozens of organized bug hunts, and more than a thousand fixes have shipped since February. The point isn't that the site is perfect — it's that we treat the site like an operational system, and operational systems have a maintenance loop.
There's more under the hood — a media vault, a proper RBAC system that respects scope and authority, conflict-resolution workflows, two cron systems wrangling background work — but the fly-by above is the part that affects you day to day.
The bug queue: reports filed by members, triaged by severity.
Awards are their own system now. Medals and ribbons are designed in the platform (there’s a ribbon builder and a medal composer), proposed with the criteria that earn them and the ranks allowed to award them, reviewed, and then presented. Every presentation lands on the member’s record with its citation, who presented it and when. Kudos run on the same rails, right down to a Discord slash command.
Proposing a ribbon with the in-platform ribbon builder.
THE RECORD SO FAR
The capabilities matter less than what they enable.
More complex events with better-prepared crews. Multi-wing exercises that used to require manual coordination now have shared slot rosters, automatic channel routing, and an AAR template waiting on the other side.
Our boarding actions and capital ship doctrine get written down, taught, certified, and re-tested. The org gets sharper every quarter, not just every patch.
Each wing keeps its own public page.
The platform keeps moving, and most of what changes comes from members filing bugs and ideas. A few things that landed in the last few weeks:
If you find a bug, file it. If you want to write for Signal, pitch the editor. If you want to teach a course, the Academy is hungry. If you want to lead a task force, the framework is there. And if you’ve been away, your record is waiting.
Welcome to VNGD 2.0.
Editor’s note: originally published May 1, 2026 as our launch announcement. Revised October 13, 2026.
“I_Die_a_Lot commands the VSS Trogdor and VSS Miyagi, serves as XO of Defiant under CO Chakrin, and edits the Signal — Vanguard's official publication. He also built and maintains the platform you're reading this on.”
