# Sewaa Consulting > Sewaa Consulting is an independent Sitecore consultancy run by Prabh. It provides Sitecore support and maintenance, performance optimization, publishing and Solr fixes, upgrades from Sitecore 9.x to 10.x, XM Cloud readiness assessments and white-label Sitecore development for digital agencies. Clients are served remotely (Worldwide (remote)). Contact: sewaaconsultancy@gmail.com or https://sewaaconsulting.com/contact/ ## Services - [Sitecore support and maintenance](https://sewaaconsulting.com/services/#support): A monthly retainer that gives you a named Sitecore person: patches and hotfixes applied, logs watched, publishing and indexing kept healthy, and users and roles managed. You get agreed response times and a monthly summary of what was done. - [Performance optimization](https://sewaaconsulting.com/services/#performance): I find out where the time goes, using Sitecore's admin tools, your APM data and SQL and Solr diagnostics, then fix the biggest bottlenecks first. Typical work covers HTML caching, cache sizing, query rewrites, Solr tuning, database maintenance and front-end Core Web Vitals. - [Upgrades and XM Cloud readiness](https://sewaaconsulting.com/services/#upgrades): Planning and delivery for moving from Sitecore 9.x to 10.x: inventory, module compatibility, code and config changes, testing and cutover. If you're considering XM Cloud, I'll give you a readiness assessment that covers effort, risks and what changes for your editors. - [White-label support for agencies](https://sewaaconsulting.com/services/#agencies): I work as part of your team, under your brand. Use me for overflow development, Sitecore admin on client sites, out-of-hours cover or a technical second opinion before you quote. I use your ticketing, repositories and processes. - [Sitecore health check](https://sewaaconsulting.com/services/#health-check): A fixed-price review of one Sitecore environment that covers configuration, caching, publishing, indexing, security basics, logs and performance. You get a written report that ranks findings by impact and effort, so you know exactly what to fix first. - [Sitecore development](https://sewaaconsulting.com/services/#development): New components, templates and integrations for existing Sitecore sites, built to fit your solution's conventions and documented for whoever maintains them next. ## Guides - [The most common Sitecore problems, and how to fix them](https://sewaaconsulting.com/resources/sitecore-common-problems/): Most Sitecore problems fall into a handful of groups: slow pages, slow or stuck publishing, content not updating after publish, broken search and Solr indexes, xConnect and xDB errors, database growth, Experience Editor issues, deployment and config mistakes, missing security patches, and versions running out of support. Each has a known cause and a known fix, and most can be fixed without rebuilding anything. - [Sitecore content not updating after publish: causes and fixes](https://sewaaconsulting.com/resources/sitecore-content-not-updating-after-publish/): When published Sitecore content doesn't show on the live site, the item is usually not in a final workflow state, has a publishing restriction, or wasn't published in the right language. If the item did publish, the HTML cache, remote events on content delivery servers, custom code caching, or a CDN is serving the old version. Check the web database first to see which side the problem is on. - [Sitecore database growth: what to clean up and how](https://sewaaconsulting.com/resources/sitecore-database-growth-cleanup/): Sitecore databases usually grow because the EventQueue, PublishQueue and History tables aren't being cleaned, SQL transaction logs are never backed up, unused media is still stored as blobs, and xDB keeps visitor data forever. Fix the cleanup agent settings, set the right SQL recovery model or log backups, run the built-in database cleanup, and schedule SQL index maintenance. - [Sitecore deployment and configuration problems](https://sewaaconsulting.com/resources/sitecore-deployment-config-problems/): Most Sitecore deployment problems come from config patches that load in the wrong order or don't apply to the right server role, serialization that overwrites content editors created, and Sitecore DLLs replaced by different versions during the build. Use showconfig.aspx to see the real configuration, only serialize developer-owned items, and never deploy Sitecore's own DLLs from your build. - [Sitecore Experience Editor problems and fixes](https://sewaaconsulting.com/resources/sitecore-experience-editor-problems/): The Sitecore Experience Editor usually breaks for four reasons: a rendering throws an error only in editing mode, placeholder settings don't allow the component, placeholder keys changed during an upgrade so components seem to disappear, or the site's own JavaScript and CSS clash with Sitecore's editing scripts. Slowness usually comes from heavy renderings and too many components on one page. - [Sitecore security: patching and hardening basics](https://sewaaconsulting.com/resources/sitecore-security-patching-hardening/): The biggest Sitecore security risks are usually basic: security hotfixes from Sitecore's security bulletins not applied, the /sitecore admin and login pages reachable on public content delivery servers, default or shared admin accounts, and versions that no longer receive patches. Subscribe to Sitecore security bulletins, follow Sitecore's security hardening guide, and keep the platform on a supported version. - [Sitecore Solr index problems and how to fix them](https://sewaaconsulting.com/resources/sitecore-solr-index-problems/): Sitecore search problems usually mean a Solr index is out of sync with the database. The common causes are the wrong index update strategy, a Solr schema that wasn't updated after adding fields, Solr running out of memory, slow computed fields during rebuilds, and Solr versions that don't match what your Sitecore version supports. Check the Crawling log and the document count in Solr first. - [Fixing Sitecore xConnect and xDB errors](https://sewaaconsulting.com/resources/sitecore-xconnect-xdb-errors/): Most Sitecore xConnect errors come from three causes: the xConnect client certificate has expired or its thumbprint doesn't match, an xConnect Windows service such as the Search Indexer has stopped, or the xDB Solr cores are unhealthy. If your organization doesn't use personalization or analytics, switching xDB off is often the simplest and cheapest fix. - [Sitecore 9.3 to 10.x upgrade: a planning checklist](https://sewaaconsulting.com/resources/sitecore-9-3-upgrade-checklist/): Treat a Sitecore upgrade as a project with four phases. Inventory everything you have, check each module and dependency against the target version, run the upgrade in a separate environment with serialized items and config, then regression-test and cut over with a rollback plan. Decide early whether to stay on XP/XM or move to XM Cloud. - [Sitecore performance checklist: 12 fixes that matter most](https://sewaaconsulting.com/resources/sitecore-performance-checklist/): Most slow Sitecore sites get fast again once you turn on HTML caching for renderings, size the data and item caches properly, keep Solr and SQL healthy, and switch off work you aren't using, like xDB tracking. Measure first, change one thing at a time, and measure again. - [Why Sitecore publishing is slow, and how to speed it up](https://sewaaconsulting.com/resources/sitecore-publishing-slow/): Sitecore publishing slows down when people run full republishes instead of smart or incremental publishes, when the EventQueue, PublishQueue and History tables grow very large, and when each publish triggers heavy indexing and cache clearing. Clean the tables, publish smarter, and for large content volumes consider Sitecore Publishing Service. ## FAQ - **Which Sitecore versions do you support?** Sitecore XP and XM 9.x and 10.x, including SXA sites. I also run XM Cloud readiness assessments for teams deciding whether to move to SaaS. - **Do you work with agencies under their brand?** Yes. White-label work is a core service. I work in your tools, follow your processes, and stay invisible to your client unless you want me on calls. - **How does pricing work?** There are three options: prepaid blocks of support hours, a monthly retainer with agreed response times, or a fixed price for defined projects such as a health check or upgrade. You'll get a written quote before any work starts. - **Can you help with an urgent production issue?** Often, yes. Email with "Urgent" in the subject and describe the problem. You'll hear the same business day whether I can take it on right away. - **Do you need access to our servers?** For support and optimization work, yes: read access to logs and admin tools at minimum. For a first assessment I can start from exported configs, logs and a screen-share session. - **Where are you based, and which time zones do you cover?** I work remotely with clients in different time zones and agree overlap hours at the start of each engagement.