Independent AI Product Engineering & Creative Technology Studio — Barcelona

Brenych Studio builds AI-native products, controlled agent systems, developer infrastructure, interactive software, native applications, real-time 3D / XR experiences, games, spatial systems, and authored digital products.

The studio works across the full product path:

concept
→ product architecture
→ interface and interaction
→ engineering
→ cloud / agent infrastructure
→ controlled execution
→ validation
→ visual direction

The practice is not a single-category web studio. Current work sits across product engineering, agent infrastructure, games, spatial computing, native applications, and creative technology.

• Website: https://brenychstudio.com
• LinkedIn: https://www.linkedin.com/in/brenych/
• GitHub: https://github.com/brenychstudio

A significant part of current Brenych Studio work is developed in private repositories. This particularly applies to AI-agent infrastructure, proprietary product systems, games, native applications, production tooling, and experimental R&D.

The public GitHub represents only part of the studio's active engineering work. Absence of a public repository does not mean a project is conceptual.

BDB is one of the studio's principal technical systems: an independent control / governance layer between AI models and real-world actions.

It is not a replacement for Claude, OpenAI, Codex, or MCP. It is a control layer around agent execution.

Relevant design:

• controlled agent execution
• explicit authority boundaries
• READ / STAGED_WRITE / PRIVILEGED_ACTION patterns
• human approvals
• provenance
• validation
• workspace isolation
• freshness / replay handling
• auditable result evidence
• model-agnostic architecture
• product integrations

Current research and integration directions include BDB × OpenAI / Codex / Astra, BDB × Claude, MCP, and multi-agent workflows. These are active engineering directions; unfinished integrations are not claimed as production-complete.

BAF is a current production-technology system for Blender-integrated 3D work.

It is used for structured asset generation and preparation, production pipelines, validation, controlled AI-assisted 3D workflows, and reusable environment / asset production. BAF is production tooling for broader game and environment work, not a portfolio experiment.

SprintCRM is internal CRM / workflow software rather than a marketing website.

Relevant characteristics:

• React / TypeScript
• Supabase
• PostgreSQL
• Auth
• RLS
• structured CRM and outreach-workflow logic
• product-bridge / controlled-agent integration work

The live system is not publicly available; it holds private operational data.

A current agent-native interface / product experiment.

The work explores agent-native interaction, WebMCP / MCP-adjacent workflows, requirement understanding, matching, evidence, focused output, and structured brief / handoff. The intent is that AI systems can use product capabilities rather than only browse static pages. This is not a portfolio redesign.

These are connected product layers with different responsibilities, not three copies of the same SaaS product.

Weekfield → StoryForm → Distribution Desk

Plan → Create → Adapt → Publish → Track

Weekfield is the studio's creator / content intelligence and planning product.

Relevant direction:

• content planning
• visual / media intake
• structured creative workflow
• Smart Mix
• sequencing
• captions
• Week Packs
• proposal / review / apply patterns
• AI-assisted workflow with human control

Weekfield is in active product development. Commercial maturity should not be overstated from the public archive. The public website still contains an earlier CreatorOps case; the current product name is Weekfield.

StoryForm is a content / video creation system in the creator-production stack.

Relevant direction:

• storyboard-first creation
• media ingest
• video / content assembly
• deterministic rendering
• versions
• export
• human-reviewed creative workflows

Distribution Desk is a separate publishing-control layer.

Relevant direction:

• controlled publishing
• scheduling
• connected channels / accounts
• platform-specific adaptation
• revisions
• provenance
• publication records
• history / tracking

Weekfield owns what should be published. StoryForm owns creation and assembly. Distribution Desk owns whether, how, and when an approved snapshot is published.

The Territories is a flagship long-term creative and technical project: a playable interactive world rather than a WebGL demo.

Relevant direction:

• playable interactive world
• real-time 3D
• game systems
• AI-driven characters / NPC intelligence
• procedural systems
• simulation
• WebGPU
• XR research
• authored visual direction
• proprietary world / IP development

Current development is primarily private.

BLACK START is an active game / interactive IP production direction. Internal 3D production tooling such as BAF is part of how the studio prepares environments and assets for this work.

No release date, funding, or commercial outcome is claimed here.

Living Atlas is a current native / mobile application and product platform.

It is not a conceptual portfolio case. It shows that Brenych Studio works on real native consumer/mobile product development as well as web applications. Feature-level claims are kept conservative here because this public website repository does not contain the product source.

Living Atlas also informs the studio's work on context-aware and spatial interaction, but it is primarily a product, not an immersive demo.

Spatial Model Presence is a current spatial / commercial technology system for presenting products in real-time 3D.

Relevant direction:

• spatial product presentation
• real-time 3D
• interactive model presence
• premium presentation
• repeatable commercial application

This is treated as applied commercial technology, not as a visual experiment.

Whisper is a significant immersive / XR project: an exhibition system rather than a static website.

Relevant direction:

• immersive exhibition
• VR / XR
• spatial storytelling
• cinematic visual language
• sound
• presence / proximity / gaze interaction where supported
• WebXR / headset-oriented experimentation
• art and technology

A public Immersive case for Whisper is represented in this repository.

These remain useful R&D surfaces, below the flagship product layer:

• Presence OS / Memory Atlas — experimental spatial-interface / memory / presence research
• WEBHERO — living visual systems and spatial-proof R&D

House of Lune is an evolving authored product and visual-world system exploring masks, jewelry and collectible objects.

The older public archive still presents a luxury digital-maison case. That framing is no longer the primary description. Product, manufacturing, sales, and release claims are not made here; the transition is still in progress.

Brenych Studio participates in Claude for Startups, AI builder / startup programs, technical challenges, hackathons, and European AI builder community activity. This is participation, not an endorsement of Brenych Studio products by Anthropic or other programs.

Current R&D includes:

• controlled AI agents
• Claude / Anthropic ecosystem
• Claude Code
• OpenAI / Codex
• MCP
• WebMCP
• multi-agent systems
• long-running agent infrastructure
• human-in-the-loop execution
• approval systems
• provenance
• validation
• observability
• execution boundaries
• AWS-based infrastructure
• isolated workspaces
• durable state
• retry / recovery behavior

Additional experimental systems, used where they serve a concrete production or research path, include SceneReady, Agent Forge, and spatial / product-control research.

• AI-native product architecture
• controlled agent systems
• Claude Code
• OpenAI / Codex
• MCP / WebMCP
• multi-agent workflows
• human approvals
• tool execution
• evaluation
• provenance
• validation
• observability
• context / workspace isolation

• AWS
• Node.js / TypeScript
• Supabase
• PostgreSQL
• Auth / RLS
• APIs
• Edge / serverless
• Cloudflare
• durable state
• execution infrastructure

• React
• TypeScript
• Vite
• Astro
• native / mobile application development
• product interfaces
• design systems
• multilingual applications
• workflow software

• Three.js
• React Three Fiber
• WebGL
• WebGPU
• WebXR / XR
• Blender-integrated workflows
• real-time 3D
• spatial interaction
• procedural systems
• game technology

• interaction design
• visual systems
• product concept
• creative direction
• photography / visual-art background
• immersive storytelling
• digital / physical product worlds

• Build systems, not isolated screens.
• Treat AI agents as software actors with explicit boundaries.
• Keep consequential actions reviewable and auditable.
• Use explicit state, provenance, validation and evidence.
• Prefer reproducible systems over impressive demos that cannot survive real operating conditions.
• Treat interaction and visual quality as part of engineering quality.
• Use AI aggressively in development while keeping architecture, acceptance boundaries and final responsibility human-owned.

This repository powers the current Brenych Studio public website / portfolio system.

It is a public positioning surface and case archive. It is not a complete inventory of current studio engineering.

The public site operates as:

• a studio positioning surface;
• a case-backed proof archive;
• a commercial offer layer;
• a search-ready acquisition system;
• a public record of selected product and immersive work;
• a front-end demonstration of the studio's interaction and presentation standards.

The project combines editorial presentation, data-driven case architecture, route-level SEO, responsive case storytelling, immersive proof routes, and a shared inquiry system in one production React application.

Selected older website and interface cases remain in the public archive for historical proof. They do not define the studio's current product or engineering direction.

Primary public routes:

• /
• /work
• /immersive
• /offer
• /about
• /privacy
• /legal
• /work/:slug
• /immersive/:slug
• /services/:slug

Service-entry routes currently live:

• /services/premium-landing-page
• /services/product-demo-landing
• /services/interactive-web-systems

The codebase also includes hidden no-index routes used for alternate surfaces, labs, and controlled previews such as /work-lab/:slug, /studio-index, /evidence-atlas, /offer-v2, /about-v2, /immersive-v2, /privacy-v2, /legal-v2, and /spatial-proof.

The site is organized around a route-driven and data-driven architecture:

• src/data/cases.ts stores the core Work registry, including metadata, content structure, related services, links, tags, production facts, and Open Graph assets.
• src/data/workEvidence.ts and src/pages/EvidenceAtlas.tsx drive the Work archive, featured-system selection, filters, and evidence framing.
• src/data/immersive.ts powers immersive case metadata, media inventories, proof labels, links, and search-readable content.
• src/data/servicePages.ts defines the service-entry pages as structured commercial routes with shared proof references and delivery logic.
• src/data/caseStories.ts and src/data/availableSystems.ts extend the archive with deeper storytelling and adaptation-ready system framing.

This keeps content, proof structure, and visual systems separate enough to evolve without turning the site into a hard-coded portfolio.

• React 19 + TypeScript + Vite front-end application
• Route-level SEO metadata and canonical URLs
• Structured data / JSON-LD output for organization, profile, cases, and service routes
• Sitemap and robots configuration in public/
• Dedicated service-entry pages that stay outside the main navigation
• Shared project inquiry drawer across major public routes
• Immersive and case-specific media systems for image, video, inspection, and walkthrough proof
• Locale content layer with English, Ukrainian, Spanish, and Russian dictionaries in src/i18n/
• Sound preference and interface audio system via SoundProvider, useSound, and the signal dock
• Cloudflare Pages deployment with pinned Node runtime via .node-version

• React 19
• TypeScript
• Vite 8
• React Router 7
• Tailwind CSS v4
• Framer Motion
• Three.js
• React Three Fiber
• Drei
• Tone.js
• ESLint
• Sharp

src/
  App.tsx
  config/
  data/
  hooks/
  i18n/
  pages/
  stage/audio/
  store/
  ui/

public/
  cases/
  immersive/
  docs/
  og-default.png
  robots.txt
  sitemap.xml

scripts/
  optimize-case-images-to-webp.mjs
  relink-case-images-to-webp.mjs
  generate-development-playbooks.mjs

Install dependencies:

npm install

Run the dev server:

npm run dev

Run lint:

npm run lint

Build production assets:

npm run build

Preview the production build:

npm run preview

Node runtime for consistent local and Cloudflare builds is pinned in .node-version. The project currently targets:

^20.19.0 || >=22.12.0

The site is deployed on Cloudflare Pages.

For production-safe publishing, the important checks are:

• successful npm ci and npm run build
• healthy public route responses
• correct canonical domain
• valid sitemap.xml and robots.txt
• working media assets on desktop and mobile
• stable no-overflow layout on public routes

Current approved baseline tag:

v1.0.0

Use it as a stable restore point when needed:

git checkout v1.0.0

The GitHub account contains a mix of public proof, experiments, selected product repositories, and open work.

A significant part of current Brenych Studio work is developed in private repositories. This particularly applies to AI-agent infrastructure, proprietary product systems, games, native applications, production tooling, and experimental R&D.

The public GitHub represents only part of the studio's active engineering work.

If you are reviewing this profile for collaboration, engineering work, research, or a product conversation, treat the public repositories as a partial technical record rather than the full scope of current work.

• Website: https://brenychstudio.com
• LinkedIn: https://www.linkedin.com/in/brenych/
• GitHub: https://github.com/brenychstudio
• Instagram: https://www.instagram.com/rostyslavbrenych/

This repository is not a generic starter template. The code, content structure, case framing, brand language, and media direction are part of the Brenych Studio portfolio system and should be treated as authored work rather than reusable theme material.