Independent software project / Built online

Software,made with purpose.

Veyrion is a software studio concept developed by Marcu Brasovean. It explores websites, applications, backend systems, automation and interactive software, shaped by hands-on programming, web development and FTC robotics.

01 / Listen02 / Make03 / Ship04 / Stay involved
VEYRION / SYSTEM STUDYFIG. 001

WELCOME TO VEYRION

Good ideas deserve good systems.

Thoughtful software.Connected systems.Work that lasts.
CONNECTED BY DESIGNBUILT WITH PURPOSE
Backend✳Frontend✳SaaS✳Games✳Security✳Automation✳Robotics
SecurityThink about accounts, permissions and secrets early.
ClarityMake interfaces and project decisions easy to understand.
OwnershipKeep setup and maintenance understandable.
PerformanceKeep the experience responsive without unnecessary complexity.

Areas of focus.

01

Backend systems

APIs, authentication, data models and server-side logic for applications that need a dependable foundation.

Node.jsREST APIsDatabases
02

Automation that earns its place

Small tools and repeatable workflows that connect services, reduce repetitive steps and make routine tasks easier to manage.

PythonAPIsBots
03

Frontend people actually want to use

Responsive websites and interfaces built with HTML, CSS and JavaScript, with attention to clarity, speed and mobile use.

HTMLCSSJavaScript
04

Security & cybersecurity

Practical security patterns such as secure sessions, password hashing, input validation, access controls and careful secret handling.

AuthenticationValidationAccess
05

SaaS & product systems

Exploring product foundations such as account flows, admin panels, data, permissions and integrations through working prototypes.

AccountsAdminAPIs
06

Games, tools & experiments

Interactive systems, progression and world-building experiments, including procedural and automation ideas.

RobloxSystemsPrototypes

See what happens
under the surface.

Choose a system and follow the work as it moves. This is an illustrative model, not production telemetry.

VEYRION / SYSTEM PLAYGROUND INTERACTIVE STUDY
01TriggerIncoming event
02ValidateRules & permissions
03OrchestrateReliable workflow
04DeliverObservable outcome
RETRY-SAFE WORKFLOW01 — 04 / FLOW
A CONCEPTUAL INTERACTION · NO LIVE CUSTOMER DATA

Six layers. One system.

SYSTEM LAYERSSELECT TO INSPECT

Choose a layer to inspect how it fits into the system.

L3 / SERVICES

Domain services with explicit boundaries

Services own a domain. They do not reach into each other's tables. Failures are isolated; latency budgets are explicit.

Things I like building.

01Websites & applications+

Responsive websites, web applications and internal tools shaped around one clear use case. Start with the smallest useful version, then test and refine it.

02Backend & APIs+

API routes, data models, authentication, integrations and server-side features that support the interface and keep information organised.

03Automation+

Small scripts and workflows that connect services, remove repetitive manual steps and make routine tasks easier to manage.

04AI integrations+

Practical AI experiments with clear boundaries, attention to privacy and cost, and human review where it matters.

05Data & integrations+

Structured data, API connections, simple reporting and storage choices that fit the size and needs of a project.

06Hosting & infrastructure+

Application hosting, environment configuration, deployment workflows, logs and basic recovery planning.

07Application security+

Secure password handling, session controls, input validation, permissions and careful secret management as part of application development.

08Improving existing projects+

Understand the current code, fix concrete issues and improve one area at a time instead of starting a risky rewrite without a reason.

These are areas of interest and project work, not a promise of a staffed agency or fixed availability.

Shape an idea.

A planning prompt, not a quote or delivery estimate. Final scope depends on requirements and availability.

Project outlineA small prototype or focused feature.
Timeline preferenceFlexible. This is not a commitment.
Scope indicator
Small
Working styleIndependent build, subject to availability.

Tools I use and explore.

C++PythonJavaScriptHTMLCSSNode.jsExpressLinuxGitREST APIsSupabaseFTC SDKRoblox Studio C++PythonJavaScriptHTMLCSSNode.jsExpressLinuxGitREST APIsSupabaseFTC SDKRoblox Studio

Personal and team projects. Work in progress is labelled clearly; no fictional client results or performance metrics.

ROBOTICS / FTC

Esentza Robotics

FTC robot programming and hardware integration, including a Control Hub, Expansion Hub and four-wheel mecanum drivetrain.

Robot-control software, driver control and testing as part of a competition robotics team.

Milestone: The team earned a regional event win in 2025.

GAME DEVELOPMENT

WORLDBOUND

A third-person Roblox game focused on exploration, farming, creatures, progression and automation.

Procedural environments, landmark locations, interactive systems and a flexible progression loop.

Status: Concept and development in progress.

WEB PLATFORM

Veyrion website

A responsive website and backend with owner-only administration and persistent content.

Content editing, authentication, API routes and deployment checks.

Status: Ongoing project; features are tested as they are added.

See project details ↗

How I approach a project.

A suggested workflow, adjusted to the scope. It is not a claim of a staffed delivery team or fixed turnaround.

01

Understand

Clarify the goal, the people using it and the problem that needs solving.

02

Plan

Choose a sensible first version, outline the data and identify the main risks.

03

Build

Develop in small pieces so each important part can be tested as it takes shape.

04

Test

Check the main user flows, edge cases, mobile layout and error handling.

05

Release

Deploy only when the key paths work and there is a way to recover from mistakes.

06

Improve

Use feedback and real usage to decide what deserves attention next.

What guides the work.

"Useful beats impressive."

A feature should make a real task easier, not exist only to look good in a demo.

"Complexity should be earned."

Choose the simplest tool that solves the problem and can be maintained.

"Security is part of the design."

Think about accounts, data, permissions and recovery before they become an afterthought.

"Be honest about progress."

Label prototypes, experiments and finished work clearly. Do not invent results to fill a portfolio.

Start with a conversation

Send a short project brief. I will review it when available and let you know whether it fits the project's current scope. A call request is not confirmed until I reply.

Email Contact via form

Response When available

Location Online

LOCAL TIME Remote studio · --:--:-- · --

45-minute call · 09:00–16:00 in your local time