Vertex

Vertex was a modular indexing and query layer for Solana, positioned as an affordable, scalable alternative to developers running their own blockchain data infrastructure. Built and launched by a Vietnam-based team in April 2025, it offered a managed service where developers could track on-chain program state and transform raw Solana events into structured, queryable data without needing to operate low-level infrastructure themselves.

What Vertex Did

At its core, Vertex let developers create what it called indexer spaces -- isolated environments scoped to a specific Solana program ID. Within each space, a developer defined custom database tables with their own schema, wrote transformer scripts to convert raw transaction and account data into structured rows, and attached triggers tied to specific Program Derived Addresses (PDAs) to fire indexing events in real time.

The result was a per-user, per-program data pipeline that ran in the background and kept a structured database synchronized with on-chain state -- ready to query without hitting Solana RPC endpoints directly.

Architecture

Vertex was built as a multi-component system.

Geyser Plugin (Rust): The data ingestion layer. Vertex implemented Solana's Geyser plugin interface, a standard mechanism that lets validator software stream real-time account and transaction updates to external consumers. The plugin fed raw on-chain events into the rest of the Vertex pipeline.

Indexer Service (NestJS / TypeScript): The central engine of the platform. Built on the NestJS framework, it exposed API endpoints for creating and managing indexer spaces, defining tables and transformer scripts, and querying logged data. Internally it used Bull job queues for async background processing, Redis for caching and distributed state, an event emitter for intra-service communication, WebSocket listeners for real-time event consumption, and PostgreSQL for persistent structured storage. The service automatically translated user-defined schema types -- including Solana-specific types such as uint256 and varbinary -- into valid PostgreSQL column types.

Frontend Dashboard (Next.js / TypeScript): A user-facing web interface for managing indexers, inspecting data, and configuring transformers, built with Tailwind CSS and deployed via Docker and Terraform.

Landing Page (Next.js / TypeScript): A separate marketing site at vertex-sol.xyz, also containerized.

Business Model and Access

The platform operated on a SaaS basis with per-account authentication, billing, and subscription management built directly into the indexer service. This placed Vertex in the category of hosted developer tooling -- similar in positioning to services like Helius or QuickNode data APIs, but focused specifically on programmable, customizable indexing pipelines rather than raw RPC access.

The official documentation was hosted on a Notion page, and the team communicated primarily via their X account (@vertex__sol), where their bio described the product as an Affordable, Scalable and Effortless Indexing Solution.

Solana Ecosystem Context

Indexing on Solana has historically been one of the more painful developer infrastructure problems on the network. Solana's high throughput and account model make it impractical to replay history in real time, and most RPC endpoints do not retain full historical data. Projects like The Graph's Substreams, Helius webhooks, Shyft, and Carbon (a Rust indexing framework) have all tackled variations of this problem. Vertex's approach -- user-defined schemas with transformer scripts and Geyser-based ingestion -- offered a programmable, multi-tenant take on the space.

The GitHub organization (github.com/vertex-solana) contains four repositories: the geyser plugin (2 commits, Rust), the indexer service (91 commits, TypeScript), the frontend application (TypeScript), and the landing page. Development activity was limited, with the geyser plugin in particular showing minimal commits.

Current Status

As of July 2026, the Vertex website (vertex-sol.xyz and www.vertex-sol.xyz) returns NXDOMAIN -- the domain does not resolve and appears to have expired or been abandoned. The Notion documentation page is no longer rendering content. The X account shows no recent posting activity. The GitHub repositories remain publicly accessible but appear to have received no new commits since the project's early development phase in 2025.

There is no publicly documented announcement of a shutdown, funding round, team expansion, or pivot. The project appears to have been discontinued quietly after a brief period of early-stage development.