Internal tools and support desks
Kanban boards, calendars and drag-and-drop form builders with Vuetify, Vuex and FullCalendar.
Several of our Vue.js projects share one goal: let people without technical skills do complex work. A support system where staff build their own request forms, a no-code ETL platform for business users, an EdTech product with teacher-approved AI hints, and parts of Ben-Gurion University’s 80,000-page website.
The kinds of work we use Vue.js for, based on the projects below rather than a list of everything the technology can do.
Kanban boards, calendars and drag-and-drop form builders with Vuetify, Vuex and FullCalendar.
Step-by-step builders where users connect sources, preview data and schedule jobs without writing code.
Interactive components on high-traffic sites, rendered alongside a CMS.
Which part of the system it ran, and what it worked with. Every row links to the full case study.
Each one with the client’s problem, our approach and what changed.

The university's main Umbraco site: ~80,000 pages, ~1,000 editors, daily staff data imports and a zero-downtime move from Azure to AWS.

A support system that pairs a customer request portal with internal kanban, calendar scheduling and a form builder, all updated in real time.

A web-based ETL product where users build data pipelines without code, schedule recurring transfers and watch every stage in real time.

AI hints that teachers approve before students see them, one sortable course list across databases and a sign-up flow that fits solo learners.
We do not sell hours of a technology. We take on a result, and choose the stack with you. These are the services where Vue.js usually comes in.
Each one backed by at least one published client project.
Backend
Anything missing? Send us your question and an engineer will answer, usually within one business day.
Contact us.NET Core and .NET 7 with SQL Server on the support system and ETL platform, Node.js with PostgreSQL on TutorPro, and Umbraco on Ben-Gurion University.
Vuetify on the support system. For other products we follow the existing design system or build components to match it.
Yes. We plan the move component by component and keep the application releasable during the upgrade.
A spec, a Figma file or three paragraphs is enough to start.

Cookies on oski.solutions
We'd like to use analytics cookies to understand how the site is used, and marketing cookies to measure our ads. They are off unless you allow them. You can change your choice any time via “Cookie settings” in the footer. Cookie policy