Website profiles · Technology insights · Alternatives

igorski.nl

Creative technologist, sound enthusiast/composer and general open source contributor to all things audio-related, based in Amsterdam, the Netherlands.

Software & Apps Open Source

No paid content found

Visit website

Profile views 11 Outbound visits 7 Normal

At a glance

Category: Software & Apps
Language: English
Paid-content signal: No paid content foundObserved
Registered: 2003
Hosting: igorski.nlInferred
HTTPS certificate trusted: PassedObserved
Last updated: 2026-10-12 09:22

Website review

This review may include AI-generated content and is not individually verified. Domain, certificate and other facts come from the observed data on this page.

What is igorski.nl?

igorski.nl is the personal portfolio of Igor Zinken, an Amsterdam-based creative technologist and musician who works under the name "igorski." The site collects more than 20 years of his projects across music composition, audio and image processing, and open source software. Its focus is the creative and experimental use of technology: making tools do things they weren't necessarily designed to do, rather than just making everyday tasks easier.

The work appears in several formats: online applications, downloadable software, streaming media, open source repositories, and written case pages documenting older projects. Audio-related tools are a recurring theme, and some of the custom processing tools he uses in his own music are freely available on the site. His musical output, largely under the pseudonym Drosophelia, combines traditional instruments with those custom-built audio tools.

Who it's for

Musicians and producers curious about unusual audio processing tools, especially those released as open source.
Developers and technologists interested in open source projects around audio and image processing.
Listeners who want to explore the music and the technical process behind it.

What to look at first

If you're mainly interested in the software, start with the apps and plugins section, then browse the open source repositories for anything you might want to use or adapt. If the music interests you more, the project pages and streaming media give the clearest picture of how the custom tools feed into the compositions. The "Latest updates" section is the quickest way to see what's currently active rather than what's archived.

As a next step, decide which side of the site matches your interest: practical tools you can download and try, or documentation of past experiments. The legacy case pages are worth reading if you want context on how a project evolved, but they are less useful if you just want something to use today.

What open source audio software and plugins has Igor Zinken released?

Igor Zinken (igorski) develops open source software with a strong audio focus, alongside image-processing work. His site presents these as online applications, downloadable tools, repositories and documentation pages rather than a commercial product line.

Audio tools and projects named on the site

Phlegetron — listed among his latest updates, indicating an active audio-related project.
Gyne — another current project entry, audio-related based on the site's framing.
Swing Low and You'll Never Miss — appears in the latest updates, suggesting a musical release or audio work rather than a utility.
Custom audio processing tools — used in his own compositions under the alias Drosophelia, combining traditional instruments with software he built and makes freely available.
"igorski apps + plugins" — a section grouping his applications and plugins, which is the best starting point for browsing what is actually downloadable or runnable.

Who this is for

Musicians and producers curious about unusual processing rather than polished commercial plugins.
Developers interested in open source audio and image-processing code they can inspect or adapt.
Listeners following his music releases under aliases such as Drosophelia.

How to approach it

Start with the "igorski apps + plugins" section on igorski.nl, since that is where the working tools are collected. If you want to judge whether a tool fits your setup, check whether it runs in the browser or needs a download, and whether the source is published — that distinction matters more than the project name. The site itself notes that some pages document legacy projects, so expect a mix of actively maintained tools and historical archives.

For context on open source audio software more broadly, GitHub hosts many comparable projects, and KVR Audio maintains a database of plugins where you can compare formats and platforms.

How can I use igorski's online audio applications and tools?

igorski.nl is the portfolio of Amsterdam-based creative technologist and musician Igor Zinken, who builds open-source audio software — online apps, downloadable plugins, and tools he also uses in his own music under the alias Drosophelia. The site itself is a hub for his audio-related projects rather than a single product.

Ways to use the tools

In the browser, for quick experiments. The online applications are the lowest-friction entry point: open one, start manipulating sound, and see how it behaves. Useful if you want to test an audio idea without installing anything.
As plugins inside your DAW. The released instruments and effects are meant to be loaded into a music production setup, so you can compose or process audio with them alongside your existing tools.
As source code. Because the projects are open source, developers can read, fork, or adapt them — helpful if you want to learn how an audio effect is implemented, or need a starting point for your own tool.
As documentation of past work. The site's case pages describe legacy projects in detail, which is useful for understanding the design thinking behind a tool before you commit to it.

A practical starting point

Decide first whether you want to make sound or study how the sound is made. If you want to make music, try a browser app or install a plugin and use it in a short session — treat it as an effect or instrument in a real project rather than judging it in isolation. If you want to learn, open the repository and trace one effect from input to output; the code is the most detailed description of what the tool actually does.

For a broader set of free audio tools to compare against, Ardour covers recording and mixing, while VCV Rack offers a modular environment for patching synths and effects.

What is Drosophelia and where can I listen to the music?

Drosophelia is the main pseudonym Igor Zinken uses for his music. Based in Amsterdam, he composes under that name with traditional instruments combined with custom audio processing tools he has built himself, and the results are not the coffee-house singer-songwriter kind — expect experimental, technology-driven composition rather than straightforward acoustic folk.

Where the music lives

The site presents igorski's work across several formats: online applications, downloadable software, streaming media, open source repositories, and written case pages documenting older projects. Music released under Drosophelia fits into that same portfolio approach, so the practical route is to look for the streaming media and release entries on igorski.nl rather than expecting a separate artist site.

If you want to hear the music alongside the tools that shaped it, treat the site as the hub: the audio processing software he offers freely is the same lineage of tools used in the Drosophelia recordings, so listening and then trying the software gives you both sides of the project.

A sensible next step

Start with the "Latest updates" section on the site to see what has been released or published most recently, then follow whichever format suits you — streaming if you just want to listen, or the repositories and downloads if you are more interested in how the sound was made. For a listener who is also a tinkerer, that combination is the real draw: you can hear a piece and then open the tool behind it.

Which legacy projects and case studies are documented on igorski.nl?

igorski.nl documents a portfolio of more than 20 years of Igor Zinken's work, presented partly as "wordy case pages documenting legacy projects." The page's own update headings name specific projects: Phlegetron, Swing Low and You'll Never Miss, and Gyne, alongside a section for igorski apps + plugins. The site describes the work as spanning online applications, downloadable software, streaming media, and open source repositories, with audio and image processing as recurring themes.

What the case pages are for

The legacy write-ups suit readers who want process and context rather than a polished product page: how a tool was conceived, what it was used for, and what survived. That makes them useful if you are researching independent music-software practice, looking for prior art before building your own audio tool, or curious how a composer's custom processing tools connect to finished music. The apps and plugins section is the more direct route if you simply want something to use.

How to approach the site

Start with the "Latest updates" list to see which projects are currently active, then move to the legacy case pages for the historical ones. A reasonable decision rule: treat the case pages as reading material and the apps/plugins as working resources, since the portfolio mixes both without a single catalogue structure.

For related independent audio-software work, GitHub hosts many of these open source repositories, and Internet Archive can help locate older or discontinued web-based music tools.

How can I contribute to or get support for igorski's open source projects?

igorski.nl is the personal portfolio of Amsterdam-based creative technologist and musician Igor Zinken, who publishes open source software — often audio- and image-related — under the “igorski” moniker. The site presents projects as online applications, downloadable software, repositories and case pages rather than as a support portal, so the practical route is to reach the specific project’s own code home.

How to contribute

Find the project’s repository first. The site describes its output as “open source repositories” and “wordy case pages documenting legacy projects,” so each tool (for example Phlegetron, Gyne, or the audio plugins) is likely to have its own codebase and issue tracker. Contributions belong there, not on the portfolio page.
Match the contribution to the project type. For browser-based instruments and apps, expect front-end and Web Audio work; for plugins, expect platform-specific build and audio-DSP work; for utilities, smaller fixes and documentation are often the easiest entry points.
Read the case page before the code. Because Igor documents legacy projects in long-form case pages, those pages are the best source for design intent, known limitations and what a project is not meant to do. A patch that respects the original scope is far more likely to be accepted.
Start with something small and verifiable. A reproducible bug report, a fix with a clear before/after, or an improvement to build/installation notes is more useful than a large unsolicited refactor.

How to get support

Use the project’s issue tracker for bugs and questions, and include your operating system, browser or host version, and exact steps to reproduce.
Expect best-effort support. This is a solo portfolio of 20+ years of projects, not a company with a support desk. Some listed projects are explicitly legacy, so a fix may never come.
Check the site’s “Latest updates” section to see which projects are currently active before investing time in one.
For general contact, the site identifies Igor as Amsterdam-based and active in open source audio; a polite, specific message referencing the exact project is the realistic channel.

Choosing where to spend effort

Your goal	Best starting point	Trade-off
Fix a bug you hit	The project’s repository issue tracker	Fastest path, but response time is uncertain
Learn how a tool works	The site’s case pages and project pages	Rich context, less step-by-step help
Add a feature	Repository, after discussing scope	High value if aligned with the author’s intent
Get usage help	Project documentation, then tracker	Community answers may be sparse

A concrete next step: pick one project you actually use, read its case page for stated scope, then open the linked repository and search existing issues before filing anything new. That single habit avoids most duplicate reports and makes any contribution you do send much easier to act on.

What "open-source UI element library" actually means

The term gets used loosely, so it helps to separate the parts:

Open-source: the code is publicly available, and the license tells you what you may do with it—copy, modify, redistribute, or use commercially.
UI element: a single, self-contained piece of interface, usually small enough to read in one sitting. A button with hover states, a pricing card, a search field.
Library: a browsable, searchable collection of those elements, typically contributed by many different people.

On a site like Uiverse, elements are shared by a community and written in plain CSS or Tailwind. You find one you like, copy the markup and styles, paste them into your project, and adjust colors, spacing, and text to fit. There's no package to install and no build step required—which is exactly the appeal, and also the source of most of the confusion.

Element library vs. UI framework: the core differences

Dimension	Open-source UI element library	UI framework / design system
Unit of reuse	A single snippet you copy	A component you import or call
Installation	None; paste into your code	Package install, config, sometimes a provider
Consistency	Depends on you; each element may look different	Enforced by shared tokens and APIs
Theming	Manual edits per element	Central theme/config file
Updates	You own the copy; no upstream updates	Version bumps bring fixes and changes
Accessibility	Varies per contributor; must be checked	Usually tested and documented
Best for	Prototypes, landing pages, small sites, one-off needs	Multi-page apps, teams, long-lived products
Learning curve	Low—read the CSS	Higher—learn the API and conventions

The table isn't a verdict. It's a map of trade-offs. Element libraries win on speed and freedom; frameworks win on consistency and maintenance.

Licensing and attribution: what to check before you paste

This is where people get into trouble, and it's worth slowing down for.

Find the license. Every element or collection should state one. Common open-source licenses include MIT, Apache-2.0, and BSD. Some projects use copyleft licenses like GPL, which can impose obligations if you redistribute your code.
Understand what the license permits. MIT and Apache-2.0 are permissive: you can typically use the code in commercial and closed-source projects. Copyleft licenses may require you to release derivative source under the same terms.
Check attribution requirements. Permissive licenses usually require you to keep the copyright notice and license text somewhere in your project. That's a real obligation, not a formality.
Look for per-element terms. On community sites, the site's overall terms and the individual contributor's stated wishes may differ. If a contributor asks for credit, honor it.
When in doubt, ask or avoid. If a snippet has no license at all, you don't have clear permission to reuse it. Treat "no license" as "not open source," even if the code is publicly visible.

This article is general information, not legal advice. For commercial products with real exposure, have someone qualified review the licenses you're relying on.

How to use a community element in your project: a practical workflow

Here's a repeatable process that avoids most of the usual mess.

1. Start from a real need, not a browsing session

Decide what you need first—"a compact primary button with a loading state"—then search. Browsing aimlessly produces a pile of pretty snippets that don't fit together.

2. Copy the smallest version that works

Take the markup and the styles. Strip anything you don't need: demo wrappers, extra animations, decorative layers. Less code means fewer surprises.

3. Convert it to your conventions

If your project uses design tokens or CSS variables, replace hard-coded values:

/* Before: hard-coded */
.button { background: #4f46e5; border-radius: 8px; }

/* After: token-based */
.button { background: var(--color-primary); border-radius: var(--radius-md); }

This one step is what keeps a copied element from looking like a foreign object in your UI.

4. Check accessibility before you ship

Community elements vary widely here. Verify at minimum:

Keyboard focus is visible and the element is reachable by Tab.
Color contrast meets WCAG AA (4.5:1 for normal text).
Interactive elements use semantic HTML (<button>, not a clickable <div>).
Form inputs have associated labels.
Motion respects prefers-reduced-motion.

5. Test in context

Paste it into a real page with real content. Long labels, small screens, and dark mode break more copied elements than anything else.

6. Note where it came from

Keep a short comment or an internal credits file: source, license, date. Future you—and your legal reviewer—will be grateful.

Where element libraries genuinely shine

Prototypes and demos: you need something clickable today, not a design system.
Landing pages and marketing sites: a handful of distinctive elements, each custom.
Filling gaps: your framework lacks one specific component, and you don't want to build it from scratch.
Learning: reading well-made CSS is one of the fastest ways to improve.
Small projects: a personal site doesn't need a theming architecture.

Where they fall short

Consistency at scale: ten elements from ten contributors rarely look like one product.
Maintenance: you own every copy. When your design changes, you edit each one.
Accessibility debt: you inherit whatever the contributor did or didn't do.
No upstream fixes: a bug fixed in the original won't reach your copy.
Integration friction: different naming conventions, different units, different assumptions about resets.

When to choose which

Choose an element library when the scope is small, the timeline is short, or you need a few distinctive pieces rather than a whole system.

Choose a framework or design system when multiple people build multiple screens over months, when consistency is a product requirement, or when accessibility and theming need to be guaranteed rather than checked.

A hybrid works well for many teams: adopt a framework for the structural components—forms, navigation, layout—and borrow individual elements for the places where you want personality. Just route every borrowed element through the same token and accessibility checks, so it lands as part of your system rather than beside it.

The short version: open-source UI element libraries are a fast, flexible way to get good-looking interface pieces into a project. They are not a substitute for a design system, and the license and accessibility details are the part worth reading carefully.

Website Overview

An established domain and managed infrastructure suggest continuity of operations and may support dependable delivery, although neither guarantees service quality. Page metadata, canonical configuration and social previews work together to provide more consistent search and sharing presentation.

Domain and Registration

Registered in 2003, this domain has about 23 years of history. That suggests continuity, although ownership and purpose may have changed. The domain uses the common .nl extension, which is not an independent safety signal.

DNS and Email

Nameservers are provided by cloud86.nl, indicating managed DNS hosting. MX records point to the igorski.nl email service. SPF and DMARC are configured. DKIM status is unknown. TXT records include verification markers for Google. Such markers may also remain after a service stops being used. DNSSEC signatures were not detected, so this additional DNS authenticity protection is not confirmed.

TLS and Certificates

The public key uses EC with 256 bits. The server supplied a complete certificate chain. No organization name is present in the certificate; the available fields are consistent with domain validation. The certificate was issued by Let's Encrypt, commonly associated with automated certificate services. The certificate's total validity is about 89 days, consistent with a short renewal cycle.

HTTP and Browser Security

X-Powered-By exposes backend information: PHP/8.3.35. The response lacks these common security headers: X-Content-Type-Options, Referrer-Policy, Permissions-Policy. No obvious internal addresses or debug information were found in the headers. The Server header contains the custom value LiteSpeed. No explicit CDN or WAF marker was found in the response headers.

Technology Stack Analysis

The public page identifies PHP without precise versions, leaving fewer clues for version-specific scanning.

Search and Social Sharing

The title has 59 characters, within a common display range. A meta description is present, with 150 characters. The observed directives allow indexing and link following. No Generator meta tag is publicly exposed. A viewport declaration is present, providing a basis for mobile layout.

Hosting and Email

DNScloud86.nl

Hostingigorski.nl

Emailigorski.nl

Approximate IP geolocation (inferred; a CDN or proxy may differ from the origin server) The Netherlands Inferred 45.82.191.211

Open approximate map on OpenStreetMap

Registration details

RDAP / WHOIS

Registrar	Registrar.eu
Registered	2003-01-31
Expires	Unknown
Domain status	active
Nameservers	ns1.cloud86.nl、ns2.cloud86.nl、ns3.cloud86.eu
DNSSEC	unsigned

DNS records

DNS

Type	Name	Value	TTL	Priority
A	igorski.nl	45.82.191.211	7925	—
MX	igorski.nl	igorski.nl	14400	10
NS	igorski.nl	ns1.cloud86.nl	14440	—
NS	igorski.nl	ns2.cloud86.nl	14440	—
NS	igorski.nl	ns3.cloud86.eu	14440	—
TXT	igorski.nl	google-site-verification=E4c-HrnlWrQXAaXiBPemSqkQ3NVz8miCYdtZHtgOG40	14400	—
TXT	igorski.nl	v=spf1 +a +mx +ip4:45.82.191.211 -all	14400	—
CNAME	www.igorski.nl	igorski.nl	14400	—
DMARC	_dmarc.igorski.nl	v=DMARC1; p=none; sp=none;	14400	—

TLS and certificates

TLS / SSL

Assessment	Normal configuration
Supported protocols	TLSv1.2、TLSv1.3
Negotiated protocol	TLSv1.3
Certificate subject	igorski.nl
Issuer	Let's Encrypt
Valid until	2026-12-05T19:54 · Remaining when checked: 54 days
Verification details	Certificate trust: Passed · Hostname match: Passed

HTTP response headers

HTTP

Header	Value
content-type	text/html; charset=UTF-8
server	LiteSpeed
strict-transport-security	max-age=15768000; includeSubDomains
content-security-policy	frame-ancestors 'none'
x-frame-options	DENY

Identified technologies

PHP

Pages, Search and Sharing

Meta description	Creative technologist, sound enthusiast/composer and general open source contributor to all things audio-related, based in Amsterdam, the Netherlands.
Canonical URL	https://www.igorski.nl/
Language	English (default)
Twitter Card	Not detected

Social Sharing Preview

6 fields

Sharing metadata

og:url	https://www.igorski.nl(opens in a new tab)
og:type	website
og:image	https://www.igorski.nl/images/image_rel.jpg(opens in a new tab)
og:title	Igor Zinken - Creative technologist & musician \| igorski.nl
og:site_name	igorski.nl
og:description	Creative technologist, sound enthusiast/composer and general open source contributor to all things audio-related, based in Amsterdam, the Netherlands.

robots.txt (opens in a new tab)

16 rules

All bots 0 allowed · 16 disallowed

Disallow/oauth/
Disallow/assets/*.html$
Disallow/assets/*.woff$
Disallow/assets/applications/*.jpg$
Disallow/assets/applications/*.jpeg$
Disallow/assets/applications/*.json$
Disallow/assets/applications/*.gif$
Disallow/assets/applications/*.png$
Disallow/assets/applications/*.txt$
Disallow/assets/applications/*.webp$
Disallow/download/retrieve/
Disallow/efflux/load
Disallow/websid/load
Disallow/game/
Disallow/mailing/
Disallow/stat/

Sitemaps

https://www.igorski.nl/sitemap.xml(opens in a new tab)

User reviews (0)

No reviews yet.