ashwa@rvce — bash
IT Subsystem · RVCE

INFORMATION
TECHNOLOGY

Engineering the digital backbone of Ashwa Racing — from the website you're reading to the systems that keep the car on track.

4Domains
6Roadmap Goals
Commits

The Digital
Engine Room

The IT subsystem drives digital innovation at Ashwa Racing — from the public-facing website to the internal tooling that powers day-to-day operations.

Our responsibilities span the team's custom ERP platform, driverless simulation and machine learning systems, data acquisition pipelines, and the broader technology ecosystem that keeps Ashwa Racing scalable, secure, and efficient.

If it involves code, infrastructure, or data — IT owns it.

typescript ashwa-it.ts
type Domain =
  "web" | "ml" | "erp" | "infra";

interface AshwaIT {
  domains: Domain[];
  mission: string;
  deploy: () => Promise<void>;
}

const it: AshwaIT = {
  domains: ["web", "ml",
           "erp", "infra"],
  mission: "build fast, ship often",
  deploy: async () => {
    await push("production");
  }
};

Four Pillars,
One Stack

01

Website Development

Building and maintaining Ashwa Racing's digital presence with modern web standards, performance-first architecture, and editorial-grade design.

HTMLCSSJavaScriptUX
02

Driverless ML

Developing perception, planning, and control models to support autonomous racing simulations across the Ashwa driverless programme.

PythonPyTorchROSSLAM
03

Custom ERP

In-house management tooling for inventory, documentation, resource planning, and workflow automation — built for how a Formula Student team actually works.

Node.jsMongoDBReactREST
04

Systems & Infrastructure

Servers, APIs, CI/CD pipelines, version control, and deployments — the invisible layer that keeps everything else running.

LinuxGitDockerCI/CD

Where We're
Going

Fast. Automated. Scalable. Reliable. Our long-term vision is a digital ecosystem that makes smarter engineering decisions possible, reduces manual effort across every subsystem, and builds tooling that outlasts any single season.

In Progress
01

Migration to MERN Architecture

Transform the static site into a fully dynamic, component-driven platform with unified API, real-time content updates, and improved long-term maintainability.

65% complete
Planned
02

Unified Data & Telemetry Hub

A web-based interface centralising vehicle logs, test run analytics, sensor health, and simulation outputs as a single source of truth for all subsystems.

Scoping phase
Active
03

Automation & Internal Tooling

Scripts, dashboards, and automated workflows that eliminate repetitive manual work — giving every team member more time for actual engineering.

45% complete
Research
04

Driverless ML Advancement

Expanding simulation capabilities, improving perception pipelines, and integrating real-time model evaluation for full autonomous stack validation.

Research & prototyping
Planned
05

Design System & UI Standards

A unified design language for all Ashwa software — visual consistency, accessibility, performance, and faster development cycles across every product.

Foundations laid
Active
06

Knowledge Base & Documentation Hub

A centralised repository of tutorials, onboarding guides, and technical documentation — making learning fast and reducing dependency on institutional memory.

30% seeded