VECTOR

Focused software. Built for the edge.

Vector builds independent game software with a focus on clarity, safety, and performance. Three products. Three clear jobs. One standard.

3 catalogue productsWindows softwareOne Vector account

[01] / The catalogue

3 products

01

Available

Minecraft 1.21.11 Ghost Client

Combat, awareness and utility tooling for Minecraft 1.21.11.

  • 33 configurable modules across three workspaces.
  • Combat assistance, overlays, movement and inventory utilities.
  • Dedicated server inspection tools.

Architecture

One client core. Configurable modules. Built-in inspection and safety tooling.

02

In development

CS2 External Skin Changer

An external CS2 cosmetic loadout tool, currently in development.

  • Planned external desktop loadout editor.
  • Planned searchable weapon and finish catalogue.
  • Planned reusable cosmetic presets.

Material composition flow

A focused material flow for finish, wear, and reusable presets.

03

In development

CS2 Mirador

A shareable external CS2 map overview, currently in development.

  • Planned live external map overview.
  • Planned browser viewer for trusted friends.
  • Planned scoped, expiring share links.

Match intelligence flow

Planned private overview and scoped sharing.

One account

Three products. One Vector account.

Manage settings, releases, and access for every Vector product from a single account.

Simple operations

Unified dashboard

Product access

Releases and downloads

Account security

Built to last

Software that stays operable.

Product state, access, releases, and delivery stay under one server-managed system from catalogue to launch.

3

Catalogue products

1

Current release

Server

Verified access

Admin

Managed content

Two-person studio

Diego + Nawer

Small by design. Accountable end to end.

Vector is built and operated by Diego and Nawer. Two people stay close to the code, the product decisions, the release process, and the users relying on every build.

We design native tools, the services behind them, and the delivery path that connects both. Keeping product engineering and operations in the same hands lets us move deliberately, explain decisions directly, and maintain what we ship.

Direct product ownership

Deliberate, current releases

Support without handoffs

Long-term maintenance

Product engineering

Focused Windows software shaped around one clear job, with performance and usability treated as product requirements.

Platform operations

Account access, authenticated delivery, release controls, monitoring, and recovery are maintained as part of the product.

Working relationship

Short feedback loops, direct communication, scoped releases, and no layers between the people using the software and the people building it.

Edge starts here.

One account for catalogue access, releases, downloads, and account security.