Giuseppe.Rega
itContact

Services

I work on projects where the backend is the hard part: integrations, data, authentication, deployment. Below is what I do, and the real system where I have already done it.

.NET APIs and backends

I design and build REST APIs in .NET with Entity Framework and PostgreSQL or SQL Server: JWT authentication, roles and permissions, validation, rate limiting, logging and versioned migrations.

  • Authentication and authorisation (JWT, OAuth 2.0 client credentials, SSO)
  • Data modelling and queries that perform, not just generated CRUD
  • Documented routes and stable contracts with the frontend

Where I did it: CRI Hub

Azure and systems integration

Azure Functions, third-party service integration and complex T-SQL stored procedures on SQL Server — the work I have been doing for four years on enterprise applications for INAIL.

  • Azure Functions and OAuth 2.0 client-credentials flows
  • Integrating third-party vendors into existing application ecosystems
  • Optimising complex queries and stored procedures

Where I did it: Professional experience

E-commerce and full-stack platforms

An online shop is not an installed theme: it is server-side shipping calculation, payments, GDPR, historical pricing, product feeds and technical SEO. I have built all of it end to end.

  • Checkout, PayPal payments and consistent order state
  • GDPR compliance, consents and multilingual legal documents
  • Technical SEO: structured data, sitemap, performance

Where I did it: A Casa di Dante

AI integration in real products

I connect language models to real products with the controls that make them safe to run: spend ceilings, rate limiting, prompt-injection defences and answers grounded in your own data.

  • Assistants that answer only from your content, without inventing
  • Daily budget with a graceful fallback when the ceiling is reached
  • Assisted content generation, with human review as a hard requirement

Where I did it: This site

Containerisation and automated deployment

Docker, docker-compose, reverse proxy and GitHub Actions pipelines on self-hosted runners: from a push to main to an updated service, with no manual steps.

  • Multi-stage Dockerfiles, including ARM64
  • CI/CD with self-hosted runners and reproducible deployments
  • HTTPS, reverse proxy, rate limiting and logging

Where I did it: Every project

Does your project look like one of these?

Tell me what you need to solve. I reply within one business day with an honest assessment — including when the answer is that I am not the right person.

Contact