Desktop App Build and Code Signing for Windows

Distributing a Windows application without code signing guarantees trouble with SmartScreen and Windows Defender. Even if the app is completely safe, users see an 'Unknown Publisher' warning — and in 30% of cases, they abandon the installation. For commercial products, each lost installer means missed revenue. According to Microsoft, signed applications are blocked less often. An app signed with an EV certificate removes all warnings; an OV certificate builds reputation over time. We configure the build and signing process so that installation proceeds without extra dialogs, making your product look professional. The certificate cost runs a few hundred dollars per year but pays off through user trust.

How to Configure a Desktop Application Build for Windows

Electron + electron-builder is the most common stack for cross-platform applications. It lets you create installers for Windows, macOS, and Linux from a single codebase. A typical configuration looks like this:

# electron-builder.yml
appId:   com.company.appname
productName: AppName

win:
  target:
    - target: nsis    # standard installer
    - target: zip     # portable version
  icon: build/icon.ico
  sign: true

nsis:
  oneClick:        false
  perMachine:      true
  allowToChangeInstallationDirectory: true

WiX Toolset is used for creating MSI packages required in enterprise environments with SCCM/Intune. MSI enables centralized installation and updates. A simple .wxs example:

<!-- product.wxs -->
<Product Id="*" Name="AppName" Version="1.0.0" Manufacturer="Company">
  <Package Compressed="yes" />
  <Directory Id="TARGETDIR" Name="SourceDir">
    <Directory Id="ProgramFilesFolder">
      <Directory Id="INSTALLFOLDER" Name="AppName" />
    </Directory>
  </Directory>
  <Component Id="MainExecutable" Directory="INSTALLFOLDER">
    <File Source="AppName.exe" KeyPath="yes" />
  </Component>
</Product>

How to Choose an Installer Type

Your choice depends on your target audience. If your product is enterprise-oriented, go with MSI. For mass users, NSIS is sufficient.

Why Code Signing Is Mandatory

SmartScreen analyzes the digital signature and publisher reputation. Without a signature, the reputation is zero, and the system blocks installation. A signed app with an EV certificate gets immediate 'green light'. We help you choose the right certificate type and configure the process.

EV is better than OV: it provides seamless installation immediately, while OV needs time to build reputation. For most commercial products, we recommend EV.

Code Signing Procedure

Signing is performed using signtool.exe from the Windows SDK. Example:

# Signing via signtool.exe
signtool sign `
  /fd SHA256 `
  /tr http://timestamp.digicert.com `
  /td SHA256 `
  /f certificate.pfx `
  /p $env:CERT_PASSWORD `
  "dist\AppName-Setup.exe"

# Verify signature
signtool verify /pa "dist\AppName-Setup.exe"

Automated Signing in CI/CD (GitHub Actions)

- name: Sign Windows executable
  env:
    CERTIFICATE_BASE64: ${{ secrets.WINDOWS_CERTIFICATE_BASE64 }}
    CERTIFICATE_PASSWORD: ${{ secrets.WINDOWS_CERTIFICATE_PASSWORD }}
  run: |
    $cert = [Convert]::FromBase64String($env:CERTIFICATE_BASE64)
    [IO.File]::WriteAllBytes("certificate.pfx", $cert)
    & "C:\Program Files (x86)\Windows Kits\10\bin\10.0.22621.0\x64\signtool.exe" `
      sign /fd SHA256 /tr http://timestamp.digicert.com /td SHA256 `
      /f certificate.pfx /p $env:CERTIFICATE_PASSWORD `
      "dist\AppName-Setup.exe"

Auto-Update

Signing the installer is just the first step; delivering updates is equally important. electron-updater supports GitHub Releases, S3, and custom update servers. Updates download in the background, and the user gets a notification to restart at their convenience — no forced interruption. For MSI distributives, we use Windows Installer patch or a full re-built package with the new version. The update package must also be signed — otherwise SmartScreen will block installation of the patch. Delta updates reduce download size by 60-70%, critical for users with slow connections. We set up a channel system: stable, beta, nightly — each channel gets its own update branch and separate signing key.

What the Work Includes

1. Audit of your current build process — identify bottlenecks and suboptimal configurations.
2. Choice of installer type and certificate — based on your target audience.
3. Configuration of build scripts — set up electron-builder or WiX for automatic signing.
4. Integration of signing into CI/CD — configure GitHub Actions, GitLab CI, or Jenkins to sign every release securely.
5. Installation testing — verify that the app installs without warnings.
6. Delivery of documentation — describe the process and provide recommendations for certificate renewal.

We handle everything turnkey in 2–3 working days. Our team has 5 years of experience in desktop application packaging and over 50 successful projects. Contact us for a consultation — we'll evaluate your project and propose the optimal solution. Order build configuration so your application looks professional and inspires trust.

Additional Recommendations

• Store the certificate in a secure vault like Azure Key Vault or AWS KMS.
• Use separate certificates for dev and prod environments.
• Regularly check certificate expiration — expiry can block a release.
• Savings on user support after implementing signing can reach 20%.

For in-depth study, refer to the official documentation: signtool and WiX Toolset.

We regularly encounter a situation: "The site is not opening" at 3 a.m. — and it turns out that the VPS disk is full because nginx logs haven't been rotated for six months. Or the server went down under load on the day of an advertising campaign launch because the shared hosting had a limit of 50 concurrent connections. Setting up hosting and deployment is not about "where it's cheaper" but about what happens when something goes wrong. Our team helps avoid such incidents by designing infrastructure that accounts for real load patterns.

When to choose Vercel and Netlify?

Vercel is built for Next.js — deploy in one push, preview deployments for every PR, automatic CDN, Edge Functions, ISR without configuration. For frontend projects and JAMstack, it's the optimal choice: no operational overhead, time-to-deploy measured in minutes.

Real limitations: Vercel Serverless Functions run in us-east-1 by default (latency for Europe +80–100ms), Function timeout 300 seconds on Pro, Bandwidth 1TB/month on Pro. For heavy backend, you need workers or a separate server.

Netlify is closer to static sites and Edge Functions based on Deno Deploy. Build minutes are the main limitation on the free tier.

Why is Docker the foundation of predictable deployment?

"It works on my machine" — classic. Docker solves this through environment containerization. But a bad Dockerfile creates new problems.

A typical mistake: copying everything into the image without .dockerignore, resulting in an 800MB image instead of 80MB. node_modules inside the image weighs as much. Correct approach: multi-stage build.

FROM node:20-alpine AS builder
WORKDIR /app
COPY package*.json ./
RUN npm ci --only=production
COPY . .
RUN npm run build

FROM node:20-alpine AS runner
WORKDIR /app
COPY --from=builder /app/.next ./.next
COPY --from=builder /app/node_modules ./node_modules
COPY --from=builder /app/package.json ./package.json
EXPOSE 3000
CMD ["npm", "start"]

Final image: 180MB instead of 1.2GB. CI build time is reduced due to layer caching — if package.json hasn't changed, the layer with npm ci is taken from cache.

Docker Compose for local development and simple production scenarios: application + PostgreSQL + Redis in one configuration. For production on a single server, it's a perfectly viable option if there's no requirement for horizontal scaling.

More about containerization — Wikipedia: Docker.

How to set up Nginx as a reverse proxy?

Nginx in front of the application is standard for VPS and dedicated servers. Main functions: SSL termination, gzip, static files, rate limiting, upstream load balancing.

A configuration often done incorrectly: worker_processes auto — number of processes equals CPU count. worker_connections 1024 — that's 1024 per worker process. With 4 CPUs and 1024 connections = 4096 concurrent connections. For a high-traffic site, you need worker_connections 4096 and set keepalive_timeout 65.

For static assets with hash in the filename:

location ~* \.(js|css|woff2|png|webp)$ {
    expires 1y;
    add_header Cache-Control "public, immutable";
}

immutable tells the browser: don't revalidate this file even on hard refresh. This only works correctly with content-hashed filenames (which Vite/webpack do by default). Documentation — Wikipedia: Nginx.

AWS: flexibility and complexity

EC2 + Auto Scaling Group — classic for horizontal scaling. AMI with pre-installed application, Launch Template, ASG with min/desired/max instances, Application Load Balancer. When CPU > 70% for 3 minutes — scale out, when CPU < 30% for 15 minutes — scale in. Health check via ALB removes unhealthy instances from rotation.

ECS Fargate — containers without managing EC2. Deploy a Docker image, specify CPU/memory (512 CPU units = 0.5 vCPU, from 512MB memory), Fargate launches it. More expensive than Lambda, but no cold start and no timeout limitations. Suitable for long-running processes, WebSocket servers, heavy workers.

RDS for PostgreSQL with Multi-AZ: automatic failover in 1–2 minutes when primary fails. Read Replicas for scaling reads. RDS Proxy for connection pooling — Lambda functions cannot hold long-term connections, the proxy buffers this.

Kubernetes: when it is justified

K8s adds significant operational complexity. Justified when: multiple teams deploy independent services, fine-grained resource allocation per service is needed, canary deployments and blue/green without downtime are required.

AWS EKS, GKE, or managed k8s from Hetzner (cheaper). Helm charts for standard services. Horizontal Pod Autoscaler based on CPU and custom metrics (RPS via Prometheus).

For most startups and medium-sized projects, Kubernetes is overkill. ECS or Fly.io provide 80% of the capabilities with 20% of the operational complexity.

Monitoring and alerting

A server without monitoring is waiting for an incident. Minimal stack: Prometheus + Grafana (or Grafana Cloud for managed), alerting on disk > 80%, memory > 85%, CPU > 90% over 5 minutes, error rate > 1%. Uptime via Better Uptime or Upptime (self-hosted).

Logs: Loki + Grafana or CloudWatch Logs Insights. Structured JSON logs (winston, pino) are mandatory — otherwise, log searching becomes a pain.

What is included in hosting setup

• Audit of current infrastructure and load profiling
• Selection of target architecture (VPS, AWS, serverless, Kubernetes)
• Setting up CI/CD pipeline (GitHub Actions, GitLab CI) with automatic deployment
• IaC via Terraform or Pulumi (infrastructure as code)
• Configuration of Nginx, SSL certificates, HTTP/2, brotli
• Monitoring and alerting (Prometheus + Grafana, PagerDuty)
• Documentation of runbooks and team training

Additionally, contact us if you need migration from current hosting or integration with external services.

Work process

1. Audit of current infrastructure (2–5 days)
2. Selection of target architecture with load and budget justification (1–3 days)
3. Setting up CI/CD pipeline (GitHub Actions, GitLab CI) (2–5 days)
4. IaC via Terraform or Pulumi (3–10 days)
5. Setting up monitoring and alerting (2–5 days)
6. Documentation of runbooks and team training (1–3 days)

Our experience — 7 years on the market, over 50 projects, guarantee of operability after deployment.

Timeline

• Basic deployment on VPS with Docker + Nginx + CI/CD: 1–2 weeks.
• Setting up AWS infrastructure with Auto Scaling, RDS, CDN: 3–6 weeks.
• Migration to EKS from scratch: 6–12 weeks.
• Setting up Vercel/Netlify for JAMstack: 3–5 days.

The cost is calculated individually depending on complexity and scope of work. Get a consultation — we'll evaluate your architecture in one day.