SynEdgy does more than advise teams about automation. We build and support reusable engineering assets that turn practical delivery experience into patterns other teams can use.
Some projects are led by SynEdgy. Some are sponsored by SynEdgy and governed by their wider community. Others are public blueprints or supporting modules that demonstrate how we approach a particular engineering problem.
We make those distinctions explicit because authorship, sponsorship, maintenance, package ownership, and community governance are not the same thing.
Discuss your automation challenge
Sampler
Sampler is an open-source PowerShell engineering framework for scaffolding, build automation, testing, packaging, documentation, and release workflows.
It helps teams replace one-off project setup and pipeline work with reusable, versioned conventions. That means a new module does not need to start by rebuilding the same test, dependency, packaging, and publishing foundations from scratch.
Sampler is used across established DSC Community projects and continues to evolve through practical use, contribution, and feedback.
Where to learn more
For current technical usage, templates, tasks, and command documentation, use the Sampler repository and project wiki.
Chocolatey PowerShell module
The Chocolatey PowerShell module provides PowerShell commands and DSC resources for installing, configuring, and working with Chocolatey.
The repository is community-governed and includes contributions from other maintainers. Package ownership and SynEdgy sponsorship do not imply ownership of Chocolatey Software, its trademarks, or the wider Chocolatey ecosystem.
The module demonstrates practical engineering around:
- Package installation and lifecycle automation
- Chocolatey sources, settings, features, pins, and packages
- Desired State Configuration resources
- PowerShell-native interfaces and argument completion
- Enterprise package-management workflows
DSC and configuration-as-code blueprints
DscWorkshop is a public blueprint for using Desired State Configuration as part of a complete delivery system.
It brings together hierarchical configuration data, dependency resolution, automated testing, artifact creation, release pipelines, deployment scenarios, and practical learning material.
DscWorkshop was initiated by Gael Colas and substantially expanded by Raimund Andree and Jan-Hendrik Peters within the DSC Community.
Datum provides the hierarchical configuration-data foundation used by the blueprint, while Sampler.DscPipeline provides supporting build and delivery tasks.
These projects are better presented as blueprint and expertise evidence than as standalone commercial products.
PowerShell Universal engineering assets
Sampler.PowerShellUniversalTasks
Sampler.PowerShellUniversalTasks provides reusable Sampler tasks for packaging, deploying, installing, and validating PowerShell Universal modules and offline automation repositories.
It demonstrates an engineering approach where PowerShell Universal resources are versioned, packaged, and delivered through repeatable module and pipeline practices.
synedgy.universal.helper
synedgy.universal.helper provides reusable attributes and dashboard components for PowerShell Universal.
The repository includes declarative patterns for APIs and AI tools, plus components for job summaries and terminal-style job output. These helpers reduce repeated implementation while keeping common behaviour in one maintained module.
Both modules demonstrate the PowerShell Universal expertise behind SynEdgy’s platform work.
synedgy.PSSqlite
synedgy.PSSqlite is a modern PowerShell abstraction over SQLite for modules and applications that need a lightweight embedded database.
It lets developers:
- Define tables, columns, views, and schema versions in YAML
- Initialise and version the database from that configuration
- Use PowerShell-friendly CRUD commands instead of writing SQL for every common operation
- Use parameterised filters and queries
- Access direct SQL when the abstraction is not enough
The module is particularly useful for local persistence, caching, and PowerShell Universal apps or APIs that need a simple single-file backend.
What these projects demonstrate
The technologies differ, but the engineering principles remain consistent:
- Build reusable foundations rather than repeat one-off work
- Keep configuration explicit and versioned
- Automate testing, packaging, and delivery
- Make common operations easier without removing advanced escape hatches
- Document decisions and operational behaviour
- Contribute useful patterns back to technical communities
These are the same principles SynEdgy applies in Services, Expertise, and Training.
Start with your engineering challenge
You do not need to adopt one of these projects to work with SynEdgy.
The useful question is whether your team is repeatedly solving the same automation, delivery, integration, packaging, or operational problem. We can help you understand the constraint, evaluate suitable patterns, and build the right reusable foundations for your environment.
