Vinexel

Project context

What this project is trying to make possible.

Central technology foundation / research and development

Vinexel is a technology ecosystem and research-and-development centre. It creates a place where foundational technology, experiments, and practical product work can grow together without being forced into one product shape.

Vinexel provides the technology and learning base for selected portfolio projects. Its framework, language, and studio are related lines of work, but each has a different purpose and maturity boundary.

Current statusCentral technology foundation / research and development

Portfolio roleIts relationship to the other entries is foundational: it supports discovery and technical development, while each project retains its own product or market context.

Project profile

The facts behind the project, with their evidence state.

Evidence level

Vinexel is an ecosystem rather than one distribution unit. The framework and language have MIT metadata, while Studio is kept separate until its checked-in license text is clarified.

1

Distribution and licensing

Product modelConfirmed

Mixed ecosystem: open-source and unresolved child systems

The Framework and Language are published with MIT metadata. Studio is not classified as open-source or proprietary until its license document is finalized.

License and distributionNeeds clarification

MIT for Vinexel Framework and Vinexel Language; Studio requires clarification

The framework package and Vinexel Language LICENSE declare MIT. Studio contains a CSEL draft with placeholders, so it is not treated as a final license.

2

Official links

Official websiteConfirmed

vinexel.com

Listed as the package homepage for Vinexel Framework; this does not establish a separate website for every child system.

GitHub repositoryConfirmed

github.com/vinexel/vinexel

Listed as the Composer source repository for Vinexel Framework. The wider ecosystem does not have one confirmed public repository in the current audit.

3

People and development

Named developer or teamConfirmed

Elwira Perdana — Lead Developer (framework metadata)

Composer metadata names one lead developer for the framework; it does not establish the total team behind the full Vinexel ecosystem.

Development team sizeNot established

Total development team size not publicly established

No reliable public evidence for this field was identified in the current audit.

Development budgetNot established

Development budget not publicly established

No reliable public evidence for this field was identified in the current audit.

4

Ownership and business context

Parent or holding contextDeclared context

Iconic Tyrant / Tyrant Tech Imperials portfolio context

Declared as portfolio context or direction; this does not independently establish a legal or operational fact.

Client or commissioning companyNot established

Client or commissioning company not publicly established

No reliable public evidence for this field was identified in the current audit.

Ownership evidenceObserved

License notices name Iconic Group and PT Iconic Wira Niaga for the framework; full ecosystem ownership is not independently established

A copyright notice is evidence about that source file, not a complete legal ownership register for every Vinexel line.

Role in the ecosystem

One project can contain several systems.

3 systems documented

Vinexel provides the technology and learning base for selected portfolio projects. Its framework, language, and studio are related lines of work, but each has a different purpose and maturity boundary.

Parent projectVinexelTechnology ecosystem & R&D foundation

System inventory

Choose a system to inspect its own implementation boundary and evidence.

1Application framework

Vinexel Framework

A modular PHP framework for isolating multiple project applications inside one technical checkout.

Current statusActive technology foundation / shared runtime

Role in the projectCarries the reusable project boundary, HTTP lifecycle, framework services, and engineering practices used to develop separate applications.

View technical details for this system

Evidence levelConfirmed in framework repository

Repository or source boundaryvinexel-framework/

Runtime and execution contextPHP 8.3+ modular framework runtime with optional GoEngine integration

System boundary

HTTP → public/index.php → Iconic loader → system/framework → vision-serve → app/{Project}

Modules and capabilities

6

Project-scoped controllers, models, services, views, and routes

Bundled PSR-4 and classmap loader

Database, session, security, cache, and queue modules

Project-scoped HTTP host and port resolution

Optional GoEngine integration

Dependency-free framework test engine

Representative interfaces

These are representative routes found in source, not a promise that this is an exhaustive API inventory.

2

ENTRYpublic/index.php

Primary HTTP entry point for a project application

RUNTIMEvision-serve

Framework serving and project lifecycle boundary

01

Confirmed evidence

The README documents isolated applications in one checkout
The source contains project-scoped app directories and namespaces
The framework exposes a reusable HTTP and service lifecycle
The test suite includes a framework test engine

02

Still open

Production deployment topology and live runtime metrics are not established
The framework does not by itself establish the operating status of every child application
No adoption, revenue, latency, or availability metric is attached to this system

Current phase

Central reusable runtime and R&D foundation

Next practical direction

Continue hardening project isolation, security, testing, observability, and delivery practices across the shared runtime.

Longer-term possibility

Remain a durable base for multiple products without turning every product into the same application.

2General-purpose language and toolchain

Vinexel Language

A general-purpose language, compiler, runtime, standard library, integrations, GPU, and developer-tool ecosystem developed as a separate Vinexel technology line.

Current statusRust bootstrap workspace / self-hosted target under development

Role in the projectExtends the technology ecosystem toward language and systems research. It is a separate toolchain line, not an assertion that the PHP framework has been replaced by it.

View technical details for this system

Evidence levelConfirmed in language repository

Repository or source boundaryvinexel-language/

Runtime and execution contextRust workspace for the reference compiler, with capability-specific runtime and host toolchain crates

System boundary

Source .vin → lexer/parser → HIR/MIR/VinIR → passes → backend/linker/runtime

Modules and capabilities

8

Lexer, parser, CST, AST, and semantics

HIR, MIR, VinIR, verifier, and compiler passes

Cranelift, LLVM, WASM, object, and linker boundaries

Core, memory, async, IO, process, platform, and threading runtime

Standard library for collections, filesystem, networking, math, time, process, and encoding

C ABI, FFI, Node-API, WASM, and embedder integrations

CLI, LSP, formatter, package, documentation, debugger, and profiler tools

AI, tensor, GPU, and asset-pipeline domains

Representative interfaces

These are representative routes found in source, not a promise that this is an exhaustive API inventory.

4

CLIcargo check --workspace

Workspace correctness and dependency check

CLIvin version

Language and toolchain contract metadata

CLIvin link-plan --json

Deterministic linker-plan inspection output

SOURCE*.vin

Vinlang source-file boundary

01

Confirmed evidence

The root README defines Vinlang as a general-purpose language with .vin sources
Cargo.toml declares compiler, language, runtime, standard-library, tools, integrations, and GPU crates
The repository documents a Rust bootstrap and a separate self-hosted source boundary
The repository records explicit capability and release gates instead of treating every backend as complete

02

Still open

A Rust-free self-hosted release is not established by the current repository evidence
Host compiler, linker, SDK, GPU, and runtime capabilities remain target-specific
Production adoption, compatibility breadth, and release distribution are not established

Current phase

Language and systems R&D with a staged bootstrap path

Next practical direction

Continue validating compiler semantics, runtime contracts, backends, packaging, and self-hosted release gates.

Longer-term possibility

Provide a Vinexel-native language and toolchain for selected systems, AI, and application experiments.

3Desktop IDE and AI-assisted development environment

Vinexel Studio

A Wails desktop IDE that combines a Go backend, Theia browser frontend, and embedded Maestro AI and Swarm capabilities.

Current statusDesktop application architecture / release readiness separately gated

Role in the projectProvides a developer-facing workspace where projects, language tooling, terminals, debugging, source control, testing, remote work, and AI-assisted workflows can be coordinated.

View technical details for this system

Evidence levelConfirmed in studio repository

Repository or source boundaryvinexel-studio/

Runtime and execution contextWails desktop process with Go backend, embedded frontend assets, SQLite local stores, and embedded Maestro components

System boundary

Wails desktop → AppBinding → application/domain/infrastructure → Theia frontend + embedded Maestro AI/Swarm

Modules and capabilities

7

Workspace and multi-root project operations

LSP, terminal, debugging, and breakpoints

Git, extensions, settings, testing, and remote workflows

Gateway and Maestro AI or console surfaces

Maestro Swarm gateway, MCP, provider, and governance integration

SQLite-backed configuration, logs, and session history

Theia browser frontend embedded in a native desktop application

Representative interfaces

These are representative routes found in source, not a promise that this is an exhaustive API inventory.

4

DESKTOPmain.go

Native desktop entry point and asset embedding boundary

BINDINGAppBinding

Go and TypeScript application binding boundary

FRONTENDfrontend/dist

Embedded browser-based IDE frontend

GATEWAYMaestro Swarm

Embedded AI gateway, MCP, provider, and governance context

01

Confirmed evidence

The README describes a Wails desktop with Go backend and Theia frontend
main.go embeds frontend/dist and delegates startup to the bootstrap layer
The repository contains interfaces for LSP, terminal, debugging, Git, workspace, testing, remote, gateway, and Maestro surfaces
The Swarm integration documents local SQLite stores and an embedded gateway boundary

02

Still open

Release distribution, user adoption, operational scale, provider contracts, and production support commitments are not established
The presence of an interface does not prove that every integration is production-ready
No performance or commercial metric is inferred from the source tree

Current phase

Integrated desktop development environment under active engineering

Next practical direction

Continue validating the desktop shell, binding contracts, persistence, AI governance, frontend quality, and release matrix.

Longer-term possibility

Become the primary developer workspace for selected Vinexel language, framework, and AI-assisted experiments.

Development strategy

A direction that can be tested and refined.

Development strategy

Build reusable foundations, test ideas in contained projects, document what is learned, and keep each product free to develop its own market and operating logic.

01

Potential strengths

A shared environment for research and engineering
Several complementary technology lines under one ecosystem
A deliberate separation between reusable foundations and project-specific products

02

Challenges and open considerations

Keeping multiple technology lines coherent without making them unnecessarily dependent
Proving which foundations are ready to support real products
Maintaining clear boundaries between research, experimentation, and dependable delivery

Current direction

A role, a current status, and a direction.

Current phase

Central research and development foundation

Next practical direction

Continue consolidating reusable runtime, project boundaries, security, testing, and delivery practices.

Longer-term possibility

Provide a durable technical base from which other portfolio projects can be researched and developed without becoming one product.

Technical appendix

For readers who want the implementation context.

Confirmed in framework repository

The following section is intentionally secondary. It records repository evidence and technical boundaries without asking every visitor to understand them first.

View technical evidence

Source surfaceVinexel framework root and Elwira application source

The current evidence describes the shared framework and its project boundary. It does not establish the operating status of every application built on it.

RuntimePHP 8.3+ modular framework runtime with optional GoEngine integration

Source surfaceFramework README, architecture docs, and project-scoped application directories

Public surfaceFramework HTTP entry point plus isolated project routes and controllers

Implementation scopeHTTP → loader → framework → project Controller → Service → Model → Database

Capabilities and modules

6

Per-project controllers, models, services, views, and routes

Bundled PSR-4 and classmap loader

Database, session, security, cache, and queue modules

Project-scoped HTTP host and port resolution

Optional GoEngine integration

Dependency-free framework test engine

Representative interfaces

These are representative routes found in source, not a promise that this is an exhaustive API inventory.

0

No public interfaces are documented in the current source audit.

01

Confirmed in repository

The repository defines a modular multi-project PHP framework
Project boundaries are represented by isolated app directories and namespaces
The framework documents a shared runtime path for the other technology projects
Visioniconic is mapped as a project on local port 8002

02

Not yet established

Production deployment topology and live runtime metrics are not established in the public evidence
No public adoption, revenue, latency, or availability metrics are attached to the framework
The dossier does not infer that every documented module is enabled in every project

Relationship to the portfolio

Portfolio roleVinexel

Qrisbill

Potential shared technology and research foundation; no runtime dependency is claimed on this page.

Flymetrade

Potential shared framework and engineering foundation; product operations remain project-specific.

Viewpelet

Potential shared framework and engineering foundation; property workflows remain project-specific.

Galactre

Research and engineering foundation for the declared AI knowledge and learning direction.

Avarouter

Technical foundation that can support the gateway layer as its architecture is developed.

Avaread

Shared technology context for a public documentation layer.

What this project is trying to make possible.

The facts behind the project, with their evidence state.

Distribution and licensing

Official links

People and development

Ownership and business context

One project can contain several systems.

Vinexel Framework

Modules and capabilities

Representative interfaces

Confirmed evidence

Still open

Vinexel Language

Modules and capabilities

Representative interfaces

Confirmed evidence

Still open

Vinexel Studio

Modules and capabilities

Representative interfaces

Confirmed evidence

Still open

A direction that can be tested and refined.

Potential strengths

Challenges and open considerations

A role, a current status, and a direction.

For readers who want the implementation context.

Capabilities and modules

Representative interfaces

Confirmed in repository

Not yet established

Relationship to the portfolio

See the otherprojects in the portfolio.

See the other
projects in the portfolio.