What We Deliver with ASP.NET Core
- corporate portals for employees and partners with corporate account sign-in, documents, requests and reports;
- a Web API for mobile apps, React or Angular frontends and partners, with documented endpoints and access control;
- interactive Blazor screens for internal tools, when your team prefers server and UI both in C#;
- real-time updates without page reloads: new requests, order statuses, support chat messages;
- sign-in and roles: your own user database, Microsoft corporate accounts or an external identity provider;
- deployment in Docker on Linux, on a Windows server or in Azure, with logging and application health checks.
Server-Rendered Pages, Blazor or a Separate Frontend
This is the key architectural decision at the start, and it sets both the budget and future maintenance. Server-rendered pages are the simplest and most affordable option for portals with forms, tables and documents, and they index well. Blazor suits internal tools with rich interaction and keeps one language and one team, though there are fewer ready-made components than in the JavaScript world. A separate frontend in React or Angular makes sense for a large customer-facing product, especially when the same API also serves a mobile app.
When We'd Recommend Something Else
- Your company runs on the Java ecosystem and your developers and servers are set up for it: Spring Boot handles the same tasks.
- The main goal is a content site managed by marketers: Umbraco, a CMS built on ASP.NET Core, makes more sense and still lets us add custom logic.
- You need a standard online store: ASP.NET Core has few ready-made modules for catalogs and carts, so it costs more than established platforms.
Modernizing a Legacy ASP.NET Portal
Rewriting a classic ASP.NET portal in one go is risky. We stand up a new ASP.NET Core application alongside the old one and migrate sections one at a time, starting with what changes most often or slows things down most. Users keep working throughout. In parallel we update database access and authentication, which usually keep a legacy project on outdated libraries. Business logic and the database can usually be preserved, but a Web Forms interface has to be rewritten. Once the last section is moved, the old application is switched off.
Data and Security
The database is most often PostgreSQL, or Microsoft products if the company already uses them, and schema changes go through migrations so each is recorded and replayed on staging and production. We add permission checks on every action, API rate limiting and an audit log of important operations, which is a required part of the work for portals handling personal data.
What We Need from You
- Who will use the system: employees, customers or partners, and how they sign in.
- The systems to connect, such as accounting, CRM or Microsoft services.
- Your hosting and security requirements.
- For modernization: code access, the framework version and a list of key sections.
What Affects Cost and Timeline
- UI approach: server-rendered pages, Blazor or a separate frontend with an API.
- Users and access: number of roles, corporate sign-in, two-factor authentication.
- Integrations: accounting systems, CRM, Microsoft products, payment providers.
- Load and availability: concurrent users and redundancy.
- For modernization: framework version, number of Web Forms pages, test coverage.
We plan the work so that after each stage part of the portal is already live and you can reprioritize the next one.
Frequently asked questions
Do I need a Microsoft license to use ASP.NET Core? No, the framework is free. You pay for hosting and possibly other Microsoft products if you choose them.
Is ASP.NET Core suitable for a public website with SEO? Yes, pages can be rendered on the server and are indexed well. For a content site managed by marketers, Umbraco is more convenient.
Our portal runs on classic ASP.NET. How much can we keep? Business logic and the database can usually be preserved, while a Web Forms interface has to be rewritten. We give a more precise answer after a code audit.
Blazor or React? For internal tools with a small team, Blazor is often the better value. For a large customer-facing product, React or Angular.
Can the portal use our Microsoft 365 accounts for sign-in? Yes. Employees can sign in with the account they already use for work email.
Do we have to run the portal on Windows servers? No. ASP.NET Core also runs on Linux and in containers, and we deploy to the environment that suits your project.
Why Promodex
We explain architectural decisions in plain language: why server-rendered pages instead of a separate frontend, why this sign-in scheme. Across 750+ projects since 2015 we have seen how costly decisions become when nobody explains them to the client. Your portal is built by our in-house team, and after launch we keep it updated along with the platform.