Backend systems
APIs, authentication, data models and server-side logic for applications that need a dependable foundation.
Independent software project / Built online
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.
WELCOME TO VEYRION
01 / Capabilities
APIs, authentication, data models and server-side logic for applications that need a dependable foundation.
Small tools and repeatable workflows that connect services, reduce repetitive steps and make routine tasks easier to manage.
Responsive websites and interfaces built with HTML, CSS and JavaScript, with attention to clarity, speed and mobile use.
Practical security patterns such as secure sessions, password hashing, input validation, access controls and careful secret handling.
Exploring product foundations such as account flows, admin panels, data, permissions and integrations through working prototypes.
Interactive systems, progression and world-building experiments, including procedural and automation ideas.
02 / Interactive system study
Choose a system and follow the work as it moves. This is an illustrative model, not production telemetry.
03 / System architecture
Choose a layer to inspect how it fits into the system.
Services own a domain. They do not reach into each other's tables. Failures are isolated; latency budgets are explicit.
04 / Areas of focus
Responsive websites, web applications and internal tools shaped around one clear use case. Start with the smallest useful version, then test and refine it.
API routes, data models, authentication, integrations and server-side features that support the interface and keep information organised.
Small scripts and workflows that connect services, remove repetitive manual steps and make routine tasks easier to manage.
Practical AI experiments with clear boundaries, attention to privacy and cost, and human review where it matters.
Structured data, API connections, simple reporting and storage choices that fit the size and needs of a project.
Application hosting, environment configuration, deployment workflows, logs and basic recovery planning.
Secure password handling, session controls, input validation, permissions and careful secret management as part of application development.
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.
05 / Project outline
06 / Tools & technologies
07 / Selected projects
Personal and team projects. Work in progress is labelled clearly; no fictional client results or performance metrics.
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.
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.
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.
08 / Approach
A suggested workflow, adjusted to the scope. It is not a claim of a staffed delivery team or fixed turnaround.
Clarify the goal, the people using it and the problem that needs solving.
Choose a sensible first version, outline the data and identify the main risks.
Develop in small pieces so each important part can be tested as it takes shape.
Check the main user flows, edge cases, mobile layout and error handling.
Deploy only when the key paths work and there is a way to recover from mistakes.
Use feedback and real usage to decide what deserves attention next.
09 / Principles
"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.
10 / Contact
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.
Your request has been saved. It is not confirmed until you receive a reply.
ACCOUNT ACCESS
Sign in to send a project brief.
Account required for enquiries. This helps prevent spam and keeps your project history attached to you.