Loading...
Organization
Operations
Join Us
A Star Citizen Fan Project
Loading...
Dispatches from the frontier. Published by Vanguard.
I_Die_a_Lot · 05/01/2026 · 15 minVanguardians, The site you're reading this on is new. Not a refresh, not a coat of paint — a from-scratch rebuild of the platform that runs the org.
We've been quietly running it in beta for a while; today it goes live, and we wanted to walk through what it is, what it does, and what it unlocks for us.
If you're a member: most of this is going to feel like coming home to a house that had every room renovated while you were out.
If you found your way here from RSI, Spectrum, or wherever the link landed you — read on. This is what it looks like when an org takes its operations seriously.
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.
The wires between our systems are no longer held together with prayers and Discord pins.
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.
A non-exhaustive Tour
Event planning tools now support multi-event campaigns, comms channel configuration, and reusable templates. Force compositions replace spreadsheets with an interactive system — leaders define teams, ships, ground units, and individual slots, then watch members sign up for actual positions in real-time.
A real operations dashboard. Not a calendar with hopes attached — a Gantt timeline of upcoming missions, a War Room situation map, an event directory you can filter by force composition, and a Nerve Center that pulls live ops state into one view. RSVPs flow into a slot system that knows about ship hangars, role qualifications, and unit assignments. After-action reports feed the next round of training.
There's even an integrated Kneeboard giving pilots a second-screen experience during ops: mission clock, comms frequencies, nav data styled like an in-game MFD.
A full learning system. Courses with structured curricula. Certifications members actually earn through assessments. Specialist Paths that map progression from "I'd like to learn this" to "I'm qualified to teach it." SME designations auto-nominate when members hit the bar. Event slots can gate on specific qualifications. We took flight school seriously enough to build the school.
Every member has a classified-dossier profile — the same intel-shop visual language we use everywhere else. Billets, awards, unit and wing assignments, groups and squadrons, task force history, certifications, and contributions are all surfaced. Pattern indicators flag concerns to leadership ambiently, so things get addressed before they fester. Promotions, demotions, and disciplinary actions go through a real workflow with audit logs and a confirmation window for anything irreversible.
You're reading it. Six editorial sections — The Brief, Fleet Reports, Operation Recaps, Sector Intel, Org Lore, and Captain's Logs — each with its own visual identity, member-only gating where appropriate, and full block-based authoring. Members submit; the editorial team reviews; the reader gets a publication that doesn't look like every other Star Citizen blog.
Internal documentation. SOPs, doctrine, lore, training material, leadership references — organized, searchable, classified where it should be. Real-time collaboration is in flight, so multiple authors can work a document at the same time without the "wait, who has it open?" dance.
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 already run four organized bug hunts; we'll run more. 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.
LAUNCH TIMELINE
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.
This launch isn't the end of anything. The roadmap is long: deeper real-time collaboration on Codex docs, a richer situation map, more Signal layouts, ongoing polish across the dashboard, and a few things we're keeping under wraps until they're ready.
Rollout Roadmap
January 2956 — Leadership Beta.
Starting with VLC and working through Wing Commanders and Unit Leaders, we'll find the bugs, break what needs breaking, and surface any issues I missed.
Phased Rollout.
Broader membership access, assuming beta doesn't reveal anything catastrophic. (It might. That's what testing is for.) Resources and orientation materials will be provided
Newsletter Transition
The newsletter moves from PDF distribution to a gated member blog with enhanced engagement features. Your reading experience improves; distribution headaches decrease. You're already reading the future format.
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.
The site is live. The org is operating. The future is built one quarter at a time.
Welcome to VNGD 2.0.
“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.”