Brittle PowerShell scripts
Work on 5 PCs, explode at 50. No retry, no structured logging, no queue, no UI for those who don't write PowerShell. The first error stops everything.
Enterprise Software Distribution
Push software to your entire PC fleet.
Push software to your entire PC fleet.
In parallel. On-premise. Agentless.
KitPusher orchestrates Windows installations from a single console: parallel queue across multiple repositories, full audit log from day one. Your data never leaves your data center.
No agent installed
Native SMB3 + PsExec
Full audit from day one
Already in production
FITEC uses KitPusher internally to handle installation support across its user base with a small team. Result: drastically reduced intervention times, full audit, zero ghost installs.
The problem
Distributing software in the enterprise is still manual work.
Three realities every IT Manager knows. KitPusher was built to close all three.
The cloud ties you down
Per-user licensing, external-ecosystem dependency, data leaving your perimeter. For public sector, banking and compliance-heavy enterprises that's a trade-off you can't make.
Manual install burns hours
A technician opens RDP, mounts the share, launches the installer, waits, retries when it fails. Multiply by 50 PCs. There goes a week of work.
See it in action
Parallel installations in 60 seconds.
Configure multiple software across a group of PCs, launch the queue, monitor in real-time, watch the inventory update.
WIZARD → BULK CSV → PARALLEL QUEUE → REAL-TIME PROGRESS → AUTO INVENTORY
Key features
One console. Everything ICT needs.
Six capabilities that together answer "why KitPusher instead of cloud solutions, agent-based tools or custom scripts?".
Parallel multi-repository queue
Hundreds of installations in parallel, automatically balanced.
- Up to 10 concurrent global installs, 1 task per repository
- Master + N secondary repos to scale beyond SMB limits
- Automatic load balancing — no manual waves to configure
- Queue persisted on DB: server restart doesn't lose tasks
4-step wizard with Active Directory lookup
Account → Software → Machine → Confirm. No CLI, no YAML.
- Cascade Vendor → Software → Version, never miscoded again
- Native AD lookup: type username, get name/department/email
- Pre-launch check: machine ping + disk space verification
- Optional scheduling: launch at future date/time
Bulk install: N software × M machines
Import a CSV of hostnames, select the software suite, confirm. Done.
- CSV import of many hostnames at once, parsed in seconds
- N software × M machines = N×M installs in a traceable group
- Pre-launch preview: total disk, estimated time, target summary
- Bulk group navigable post-launch: every single install tracked
Automatic software inventory + full audit
Always know who has what, when it was installed and by whom.
- Navigable tree: User → Machines → Installed software
- Auto-update post-install, no manual data entry
- Complete log per step: stdout, stderr, exit code, time, operator
- Export CSV/Excel for periodic audits or compliance reports
Zero agent, SMB3 + PsExec
No resident software on target PCs. Encrypted communication via native Windows protocols. No updates to manage.
Approval workflow
External requests from chatbots, ticketing or APIs enter "Pending Approval". Admins verify with one click and approve. Native PaLoMa integration.
Built-in diagnostic tools
Registry browser with search, file system browser, remote console, processes and services. All inside KitPusher: no switching for troubleshooting.
Real-time WebSocket
Live dashboard, progress bar per step (Copy 45%, Install in progress), instant toast notifications. Zero polling, zero "reload to see".
Microsoft Teams notifications
Configurable webhooks with Adaptive Card: completion, failure, approval. Per-event filters, multiple URLs, no third-party plugin.
Native credential security
Per-admin domain credentials, encrypted AES-256-GCM with PBKDF2 600k iter. Never plaintext, never shared, decrypted only at runtime. Master key external to DB.
How it works
KitPusher in the middle. Machines around it. No agent between.
A single Windows executable + PostgreSQL database. Talks to target PCs via encrypted SMB3 and native PsExec.
SMB REPOSITORIES LEFT · KITPUSHER CENTRE · WINDOWS PCS RIGHT · ADMIN AND AD ABOVE · USERS BELOW
Internal production
How FITEC runs installation support with a small team.
KitPusher is the engine that runs our installation support.
The FITEC ICT team handles software installations for its internal user base and
clients — with a small staff. Before KitPusher, every request meant: open RDP, authenticate,
mount the share, launch the installer, wait, verify, return to the ticket. Hours per
intervention, manual errors, impossible audits.
Today requests come in via chatbot, the admin
approves with one click, KitPusher does the rest.
No RDP, no scripts, no manual audit. Time per
intervention has dropped drastically. Team capacity scaled without new hires.
Time per intervention reduced
From ticket open to install confirmed: from hours of manual RDP to a few clicks in the console.
Full traceability
Every install logged: who, what, where, when. Audit-export ready, no Excel sheet to maintain.
No agent on PCs
No resident software, no resource use, nothing to maintain or update on the target PCs.
The comparison
KitPusher vs the alternatives.
What the ICT buyer evaluates in parallel, compared on the criteria that really matter.
| PowerShell scripts | KitPusher | |
|---|---|---|
| Deploy / setup | Manual | 1-3 days |
| Agents on target PCs | — | ✓ None |
| UI for non-engineers | ✗ CLI | ✓ 4-step wizard |
| On-premise data | ✓ | ✓ 100% |
| Parallel queue + balancing | ✗ | ✓ Auto multi-repo |
| Audit + auto inventory | ✗ | ✓ Native |
| Cost for broad PC fleet | High effort | Flat rate |
| Approval workflow | ✗ | ✓ Native + chatbot |
Frequently asked questions
The questions we get most often.
How long does it take to go into production?
Typically 1-3 days. KitPusher is a single Windows executable + PostgreSQL database. No cloud, no agents to deploy. Base setup ~30 minutes, initial software catalog 2-4 hours.
Do I need an agent on every target PC?
No. KitPusher uses only native Windows protocols (encrypted SMB3 + PsExec/RPC). No resident software on targets: no resource use, no updates to manage.
Does my data stay in my infrastructure?
Yes, completely. KitPusher is on-premise: PostgreSQL DB in your data center, software repositories on your shares, audit log in your DB. No cloud, no third-party telemetry.
How do you handle domain credential security?
Each admin configures their own credentials, encrypted with AES-256-GCM and PBKDF2 600,000 iterations. Master key external to DB. Never plaintext, never shared, never hardcoded, decrypted only at execution.
How many parallel installations can it handle?
By default 10 concurrent global installs, one task per repository (to avoid SMB share saturation). Configuring more repositories (master + N secondary) scales linearly: 5 repos = up to 5 parallel installs with automatic balancing, no manual waves.
Can I integrate it with ticketing or chatbots?
Yes. KitPusher exposes REST APIs to receive external requests that automatically enter the admin approval workflow. Already integrated with the PaLoMa chatbot: user asks for software via chat, admin gets the request in KitPusher and approves with one click. Same pattern works with ServiceNow, Jira, Teams, Slack.
Let's meet for 30 minutes.
We'll show you KitPusher on your scenario.
No commercial pitch. Live demo, technical questions, concrete feasibility assessment on your PCs, software and infrastructure. If the match isn't there, we'll tell you.
Contact us for a solutionOr write directly to info@fitec.it