Idepoo Services
.NET 10 and React development
For technical buyers who want to see under the hood, and for companies extending their own engineering team with a ready one.
Why this stack
.NET 10 at the back: performance, mature testing tools, and an ecosystem that will still be here in ten years. React with Next.js at the front: server rendering for SEO and speed, components that get reused, and a large hiring market for whichever team takes the code later. PostgreSQL or SQL Server depending on your infrastructure — we run both in production.
How we work
Clean architecture with explicit layers, CQRS where read and write paths genuinely differ (not everywhere), unit tests on domain logic and integration tests on the API, CI/CD with GitHub Actions or GitLab, deployment on Docker. Code review on every change. Architecture decisions documented next to the code, not in a separate Word file.
Two ways to work together
Project — written scope, two-week deliveries, fixed price. Extended team — two to four of our engineers alongside yours, on a monthly contract, on your backlog. For companies outside Iran the second usually works better: a lower engineering cost with quality you can review in every pull request.
What you get
Code you can read
Clear naming, layering, no 2,000-line classes. The next .NET engineer can carry on.
Tests
Unit on the domain, integration on the API, and on every financial calculation without exception.
CI/CD
Every merge builds and tests; staging deploys automatically, production on one approval.
Architecture docs
Decisions and their reasons, in the repo, current with the code.
Monitoring
Structured logs; errors and performance visible from day one.
Full handover
Repository, credentials, documentation. No dependency on us after delivery.
Questions
Why .NET rather than Node or PHP?
For systems with heavy domain logic and a long life, .NET has stronger typing and testing tools and larger teams maintain it. For a simple content site, Next.js alone is enough and that is what we recommend.
CQRS everywhere?
No. Only where read and write paths really differ — product search, reporting. Everything else stays simple.
How does the extended team work?
Two to four engineers, full time on your backlog, in your tools (Jira, GitHub…), with a short daily and two-way code review.
Do you work with companies outside Iran?
Yes. Our working hours overlap Central Europe by five to six hours and the Gulf almost completely, so a daily stand-up lands at a sensible time for both sides. The contract form and the payment route depend on your jurisdiction and are settled in writing before any work starts.
How do you measure quality?
Test coverage on core logic, review of every pull request, and performance criteria written into the scope and measured at delivery.
Can we see sample code?
Yes; a sample repository with the architecture and tests, before any contract.
Describe the project or backlog in three lines and whether you want a project or an extended team. We reply within one working day.