We build public sites for brands and universities, closed portals for students, staff and dealers, and browser apps that teams work in every day. The stack is mostly .NET with React, Angular, Vue or Next.js on the front end. You own every line of it.
Each type below is linked to a client project where we built it. Most real projects mix two or three of them.
Sites that editors update on their own, with forms wired to the sales and marketing tools behind them. One codebase can serve a whole family of brands.
Closed areas where each user sees their own data: schedules, grades, payments, documents or training material pulled from the systems that own it.
Browser-based tools that people work in all day. Boards, dashboards, editors and live updates, sized for the number of users you expect next year.
Content managed in a CMS, pages drawn by a JavaScript framework. Useful when several sites with different designs need to share one set of components.
When the marketing site and the product live apart, users notice. We join them with one login, one API and content that marketing controls from the CMS.
Reports, moderation dashboards and custom editors inside the CMS, so admins stop asking developers for exports and one-off fixes.
Applicants, students, faculty and staff all use the university’s main website. It holds about 80,000 pages, takes traffic spikes of around 300 requests per second and is edited daily by roughly 1,000 people.
Auto.co.il is one of Israel’s largest car websites. For its third generation, we designed the architecture on Umbraco 15 and .NET 9 and built the core of the site.
Accessibility was in scope from the start: keyboard navigation, ARIA attributes and screen reader support, following WCAG. Images are resized on the fly. About 100,000 items came over from a legacy CRM database through import pipelines, and every old URL redirects to its new address.
All four work. We pick by the shape of the product and by who will maintain it. Our Clutch profile lists our framework focus as .NET 33%, React 27%, Angular 20% and Vue 20%.
React with Redux suits this well, and the hiring pool for future maintenance is large.
Angular gives every module the same shape, which helps when several developers work on one codebase.
Vue is light to add to a server-rendered site and easy to pick up for a mixed team.
Next.js renders pages from CMS data and fits a monorepo that serves more than one brand.
On the server side we mostly work in C# and ASP.NET Core. When a project calls for something else, we use it: the task manager above runs on Node.js with MongoDB, Redis and Elasticsearch.
Content-led sites need a CMS that editors can run without developers. Ours is Umbraco on .NET, used in classic mode or headless behind Next.js. Our Clutch profile lists Umbraco as 100% of our CMS work.
Apps such as dashboards, task tools or portals built mostly from other systems’ data often do not need a CMS. In that case we skip it and keep the stack smaller. See Umbraco development for upgrades, packages and multi-site work.
Disctopia’s marketing site and streaming app now share one Auth0 login and one API, with event banners set from Umbraco. Read the case
For HS High Stake GmbH in Karlsruhe, we work on a large business portal for the German division of a well-known company, its dealers and its employees. Modules cover product materials, staff training and more. Seven different OSKI full-stack developers have worked on it over the years.
“Guys proved to be experts in their field.”
You review real pages on a staging server throughout the build. Problems with content, design or data show up early, while they are still cheap to fix.
We list the audiences, the pages or screens they need, the systems the site must talk to and the traffic you expect. Out of this comes a scope and a fixed estimate for phase one.
Content model, data flows, hosting plan and clickable screens for the main journeys. Framework and CMS are chosen here, with the reasons written down.
Two-week sprints. You see working pages on a staging server every week, not a slide deck.
Content migration, redirects for every old URL, accessibility and load checks, then a planned switch of traffic to the new site.
Updates, monitoring and new features after launch. The code, hosting and data stay in your accounts.
Universities, automotive brands, insurance and business portals in Israel, the US, Denmark and Germany.
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.
The third generation of a leading Israeli car site: ~100K records moved from a legacy CRM into Umbraco, fast catalog search and an editor-friendly back office.
OSKI developers joined HS High Stake to build modules for a large business portal that links a German division, its dealers and its employees.
A rebuild of Alliant's web estate on current Umbraco: one modular architecture for many sites, Okta sign-in for editors and forms connected to Eloqua.
The official Danish Omoda website for the Omoda 5 EV launch, built on headless Umbraco and Next.js with dealer forms and a shared monorepo.
A login-only portal for BGU students and staff that shows each person their own schedule, grades, payments and news, built on the university's Umbraco setup.
Quotes from verified Clutch reviews of our web, portal and platform projects.
Their communication skills, speed of development, and cost were incredible.
OSKI's solutions are designed with clean code and attention to detail
They had excellent project management skills, assigning project managers and QA representatives when needed.
The best CRM for commercial real estate is the one that keeps properties, owners, comps and deals linked. We compare six options for CRE brokers, investors and sponsors by data model, integrations and price, and show when a custom data layer is worth it.
The best CRM for a SaaS company is the one that can hold product usage and subscription data next to the pipeline. We compare six CRMs by data model, Stripe sync and API, then show when a custom data layer pays off.
What it costs to build a SaaS product: hours and budgets for an MVP, a v1 for paying B2B customers and a scaled platform, cost per feature (multi-tenancy, billing, SSO, admin, onboarding, analytics) and the fees you pay after launch.
Anything missing? Send us your question and an engineer will answer, usually within one business day.
Contact usOften the deciding factor is who will maintain the code after launch. If your team already works in one of them, we usually stay with it. Otherwise we choose by the shape of the product: React for state-heavy apps, Angular for large structured portals, Vue for interactive parts of a CMS site, Next.js for headless sites. We write the reasoning down during discovery so you can check it.
If marketing or editors publish content, yes. Our main CMS is Umbraco on .NET. We are a Registered Umbraco Partner and maintain our own Umbraco packages on NuGet. A web app where users create the data, such as a task tool or a dashboard, usually does not need a CMS at all.
The Ben-Gurion University site we work on holds about 80,000 pages, serves around 300 requests per second at peak and has roughly 1,000 editors. It runs on AWS with Lucene search and a page cache that clears only the pages affected by a change.
We build for WCAG from the first component: keyboard navigation, ARIA attributes and screen reader support. On Auto.co.il this work was part of the rebuild scope. Tell us which standard or law applies to you and we include the checks in the plan.
We plan for it. Content is migrated by script, every legacy URL gets a redirect to its new address and SEO fields can be set per page. On Auto.co.il about 100,000 items moved out of a legacy CRM database this way.
Yes. From 2021 to 2025, a California software consulting company used us to build Umbraco websites and Okta integrations for its own clients. We work under NDA and under your brand.
Our Clutch profile lists an hourly rate of $25–49 and a minimum project of $1,000. The total depends on scope, integrations and content volume. After discovery you get a fixed price for the first phase.
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