Do you take maintenance afterwards?
I work with active handover: operational documentation, runbooks and a 30-day bridge. Ongoing maintenance is negotiated separately.
End-to-end .NET and Blazor applications, with identity, observability and deploy on your infra or the platform that makes most sense. Fits inside your stack, doesn't replace it.
Runs on Azure, AWS, GCP or your current infrastructure. I suggest what makes the most sense for your case.
Back to servicesYou need another internal system in production without becoming dependent on a whole squad to maintain it.
ASP.NET Core + Razor/Blazor with Identity and Entra ID
Relational database modeled with EF Core and versioned migrations
Structured logs, Application Insights and tailored dashboards
Reproducible deploy pipeline (GitHub Actions or Azure DevOps)
I work with active handover: operational documentation, runbooks and a 30-day bridge. Ongoing maintenance is negotiated separately.
Yes. I follow your standard before proposing mine. If something needs to change, I justify it first.
Fixed-scope sprints of 4 to 12 weeks. BRL or USD.
Yes, modeling is in scope. I document the schema, rules and decisions.