APIWEBADMAPP

Platform statusAll monitored systems operational.

StretchGroup
LanguagesBrands
All languages

Language family

Veylun

Betav0.2.0

Define the product once. Use it everywhere.

Veylun is a proprietary family of domain languages over one shared type substrate, VTI, so product declarations can flow from database to query to server to UI without re-declaration drift. Veylun treats the seams between product layers as the language surface. Saeril defines storage, Aelir queries it, Olyra serves and renders it, Rylae builds UI against it, Tovai styles it, Lirath exposes contracts, Envra configures runtime behavior, Shyra operates workflows, and the Veylun CLI ties the toolchain together through VTI.

The Family Thesis

Most incumbent language ecosystems are held back by one dogma:

Veylun rejects those dogmas. It does not ask one language to do every job. It gives each domain a language with native syntax, native validation, native tooling, and a shared type identity.

A type is defined once and flows from database to server to UI, type-checked, with no re-declaration. The same declared entity can be:

  • General-purpose languages assume one language can own every layer.
  • Database systems assume storage shape is separate from application shape.
  • ORM systems assume code generation can repair the gap after the fact.
  • UI frameworks assume frontend types are local declarations.
  • API schema tools assume contracts are parallel artifacts.
  • Configuration and operations tools assume strings are acceptable integration boundaries.
  • Documentation systems assume content can describe behavior without being attached to the type graph.
  • Stored by Saeril.

VTI First

VTI is the shared type substrate for the Veylun family. It is a deterministic, versioned interchange format that gives every declaration a stable identity, a structural shape, and enough domain facts for downstream languages to validate their own programs.

Today, Veylun is VTI-first.

Vela, the core language, already exists. Its deeper IR and MIR architecture is designed, but not yet built. That means the first production weaving happens through VTI: Saeril emits VTI, downstream languages consume VTI, and cross-language compatibility is enforced at the type layer.

  • VTI-first gives the family a stable product surface immediately.
  • Saeril proves declared storage types can drive the rest of the stack.
  • Vela consumption proves core language integration.
  • IR-level weaving lands after Vela has enough compiler maturity to carry it responsibly.

The Lineup

Vela is the core programming language of the family.

It targets the territory currently split across Python, R, and Rust: product logic, data transformation, systems-grade modules, and high-confidence application code. Vela is not intended to be a scripting toy or a purely academic systems language. It is the typed core that eventually lets the rest of the family compile through a shared deeper substrate.

Vela dethrones Python/R/Rust by combining productive expression, data-native ergonomics, and systems-grade confidence inside the Veylun type graph.

What Is Not In The Family

Facet is a separate standalone product. It is not part of the Veylun language family.

Facet may coexist with Veylun products and may integrate through defined product interfaces, but it is not a Veylun language, not governed by Veylun language versioning, and not part of the shared VTI language lineup.

Products As Proof

Veylun is closed-source and products-as-proof.

The languages exist to produce superior software, not to win language-design arguments in isolation. Each family member must justify itself through working product surfaces, compiler checks that prevent real classes of defects, and integrations that remove repeated declarations across layers.

The north star is simple:

Download

Veylun is in active development and has no public downloads or releases yet.

No public download artifacts are available yet for this language.

Looking for everything in one place? See the downloads index.