We keep Umbraco sites patched, working and moving forward: security and minor updates, bug fixes, small features and help for your editors. Some clients have worked with us on Umbraco since 2021. If another agency built your site, we start with an audit.
You choose the mix. Each card links to a project where we did that work, or to the reference you need for it.
Umbraco, .NET and third-party packages patched when fixes are released, tested on staging before they reach the live site.
Umbraco ships minor releases every six weeks while a version is in its active phase. Staying on the latest minor keeps the next major upgrade small.
Broken templates, failing forms, search that returns the wrong pages, jobs that stop. We find the cause, fix it and release it.
A new form, a new block, a field passed to the CRM. Small, steady releases that fit the existing components instead of a big project.
Editors who ask how to do something in the back office, permissions that need a change, a document type that no longer fits how the team publishes.
Errors, logs and background jobs watched, so a failing import or a scheduled task that stopped is found before an editor reports it.
Some of the tools we use for maintenance are our own packages. MediaRemove finds and removes unused media in the back office, and NestedPagesView gives editors a tree-style overview of deeply nested content.
Umbraco sites change hands when an agency closes, a freelancer moves on or the relationship stops working. The new team’s first job is to understand what is there. Adding features on day one is how things break.
Umbraco 13 reaches end of life on December 14, 2026, and Umbraco 7, 8 and 10 already have. If the audit finds one of these, the upgrade is planned as its own project. See Umbraco upgrade & migration
Repository, hosting, database, Umbraco back office and any deployment pipeline. We list the Umbraco and .NET versions, every package and every custom extension.
How the site is built and deployed, where content and media live, which packages have no upgrade path, and what the previous team left half done.
Security gaps, broken forms and failing jobs come first. New features wait until the site is stable.
Build and deploy steps, integrations, scheduled tasks and fragile areas, documented in your repository so the knowledge stays with you.
Scope, hours, channel and response times set in the contract. If the site runs on a version near or past end of life, the upgrade is planned as a separate project.
Support is judged over time. These three engagements show how it works in practice, with the client and the dates.
From March 2021 to May 2025, a team of 2 to 5 OSKI people built and looked after custom Umbraco websites and integrations, including Okta, under the consultancy’s name. Project managers and QA were added when a project needed them, and the team helped quickly when short-turnaround work came in. The CEO asked for more initiative when reading tickets, so acceptance criteria are now agreed up front.
OSKI developers joined in January 2021. By the time of the client’s Clutch review in January 2023, 7 different OSKI developers had worked on the portal. It spans .NET Framework 4.8, ASP.NET Core 3.1 and .NET 5 with Umbraco. Bugs were fixed quickly so the product kept working, deadlines were regularly met, and the team stayed reachable for urgent tasks.
Requests arrive continuously. We handle them in small releases: custom Umbraco Forms workflows that send leads to Salesforce and Mailchimp, new and refactored components for editors, and JavaScript and stability work, without disrupting the live site.
A university site with a thousand editors and a small lead-generation site need different support. So scope, hours, the channel for urgent issues and response times are agreed per contract, based on how critical the site is and the time zones involved.
Ongoing work on live sites, white-label support for an agency, a long-running portal, a university platform and a legacy upgrade.
Ongoing Umbraco work for Fairway Divorce: form workflows that deliver leads to Salesforce and Mailchimp, reusable components and steady support.
Custom Umbraco websites and third-party integrations, including Okta, built by OSKI for a California consultancy's own clients from 2021 to 2025.
OSKI developers joined HS High Stake to build modules for a large business portal that links a German division, its dealers and its employees.
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.
An internal platform for inspections, toolboxes and transport planning, upgraded from Umbraco 8 to Umbraco 17 on .NET 10 with daily workflows intact.
Quotes from verified Clutch reviews of long-running and support engagements.
they were quick to respond and help
They are a great team.
They answered for all our questions and were constantly in touch with us.
An AI chatbot costs from about $4,200 for a simple bot over a small set of documents to $136,000+ for a multichannel bot that acts in your systems. We break it down by scope, component and rate band, and compare running costs.
A web app costs about $9,000 for a simple internal dashboard to $480,000 for a large multi-tenant platform at Eastern European rates. We break down portals and dashboards by size and component, and show which features move the price.
Custom software costs about $14,000 to $320,000 at Eastern European rates and roughly twice that onshore in the US. We break it down by project type, component and engagement model, and show how to get an estimate you can plan on.
Anything missing? Send us your question and an engineer will answer, usually within one business day.
Contact usWhat we agree in the contract. Typical scope covers security patches, Umbraco minor updates, bug fixes, small features and change requests, help for editors, and monitoring of errors, logs and scheduled jobs. Major version upgrades and new modules are usually scoped and estimated separately.
Yes. We start with an audit of the code, packages, hosting and deployment, fix urgent issues, document what we find and then agree a support plan. Fairway Divorce’s Umbraco site was already live when we joined, and we have maintained and extended it since without a rebuild.
Response times, support hours and the channel for urgent issues are agreed per contract, based on how critical the site is and the time zones involved. We do not quote one fixed number for every client.
Yes, we can keep them running while an upgrade is planned. But Umbraco 7, 8 and 10 no longer get security fixes, and Umbraco 13 reaches end of life on December 14, 2026. For those sites, support usually goes together with an upgrade to Umbraco 17. See our Umbraco upgrade service for the paths and the process.
Our rate listed on Clutch is $25–49 per hour, and the minimum project is $1,000. Ongoing support usually runs monthly. The scope and hours are set in the contract, so you know what a month costs before it starts.
Yes. We have worked on Umbraco Cloud sites such as EducatedOn and Disctopia, and on self-hosted Umbraco on Azure and on AWS, including Ben-Gurion University’s site on AWS ECS Fargate.
Yes. Small features and integrations are a normal part of support. For Fairway Divorce we wrote Umbraco Forms workflows that send leads to Salesforce and Mailchimp. Larger pieces of work are scoped as separate projects, or handled by a dedicated Umbraco developer if you need more capacity.
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
