Menu

XSEVEN · Palermo

Products, platforms and infrastructure. Built to work.

From idea to production, XSEVEN builds digital solutions and the infrastructure that makes them reliable.

  • Products & platforms
  • Development & integration
  • Infrastructure & delivery

Some of the companies we work with

All collaborations
  • Il Post
  • MediaMiner
  • Codesour
  • Cometa
  • Hoppinger
  • Formel
  • WPP Media
  • Renmote
  • Alessi Pubblicità
years of industry experience
20+
long-term clients
9
projects delivered
50+

01 — Products & platforms

From field experience, products ready for production.

XSEVEN platforms are built on our experience in software development and infrastructure management to address practical needs. Discover what you can do with each product and who it is designed for.

Problem solved
Personal and work commitments are spread across different calendars. CalFuse connects them to reduce clashes and manual updates without exposing details that should remain private.
Who it’s for
Professionals, consultants and small teams coordinating multiple accounts and calendars.
  • Calendar Sync and Mono — One-way or two-way connections, dedicated filters and a unified view of commitments.
  • Scheduling Links and Quick Schedule — Shareable booking pages and an assistant that proposes calendar changes before explicit confirmation.
  • Insights, Spaces and Contacts — Time analysis, Life Index, shared calendars and contacts for organising appointments.

Status: XCLOUD infrastructure · Developed by XSEVEN

calfuse.io
CalFuse public homepage: calendar synchronisation and availability
Public homepage · captured 2026-10-06

02 — From idea to production

Software and infrastructure, designed together.

Four steps, one team. Every software decision accounts for where and how it will run.

  1. 01

    Understand the problem

    We start from context: goals, constraints, existing systems and people involved. Before writing code, we understand what needs to change.

  2. 02

    Design the solution

    We design application architecture and infrastructure together, because each shapes the other.

  3. 03

    Build and integrate

    We build in short iterations, integrate existing systems and automate build and test from day one.

  4. 04

    Ship and maintain

    Automated release, observability and runbooks: the system stays understandable and governable after handover.

software ↔ infrastructure01 · Product
04 Infrastructure03 Platform02 Software01 Product

04 — Field experience

From AWS to bare metal: a cloud repatriation case.

Anonymous client · case documented on our blog

Context

Production platform on AWS with EC2, RDS, S3 and managed services; monthly spend in the tens of thousands of euros, predictable traffic.

Decision

Move to dedicated Leaseweb bare-metal servers without changing the application layer.

Approach

Kubernetes on bare metal with the same images, Helm charts and CI/CD pipelines; parallel run before cutover.

Described benefits

Spend down to a few thousand euros per month, faster incident diagnosis, full infrastructure-as-code, zero-downtime cutover.

Trade-offs

High availability, backup and disaster recovery had to be built in-house: more operational responsibility for the team.

AWS → BARE METAL · LEASEWEB

EC2
Kubernetes · kubeadm
EBS
Longhorn
S3
MinIO
RDS PostgreSQL
PostgreSQL + Patroni
ALB
HAProxy + Keepalived
CloudWatch
Prometheus + Grafana
VPC / NAT
WireGuard

Project phases · about 3 months

Assessment · 2wBuild · 3wParallel run · 4wData · 2wCutover · 1d

05 — People

You talk to the people who design and run your system.

A small, focused team. The people who define the architecture are the ones who build it and answer for it.

About the company

06 — Insights

Notes from daily work on AI, software and infrastructure.

All articles

Got a product to build or a system to evolve?

Quick contact

Write to us in two minutes

Name, email and a few lines about your project. We reply within one business day.

Guided questionnaire

Tell us about your project

Three steps to describe need, technical context and priorities.