DE · EN

Call us

build 6ddc7a35 | content blog-content@417154f · 338 posts | profiles 32 · corpus 315 | ● 0 skipped | built 2026-10-21 12:35 UTC format run

$ soultec get solution/igel -o yaml$ soultec get solution/igel -o json$ soultec get solution/igel -o toml$ soultec get solution/igel -o xml$ python3 igel.pyPS> ./igel.ps1$ go run igel.go$ node igel.js

apiVersion: soultec.ch/v1kind: Solutionmetadata: name: igel locale: en labels: vendor: IGEL Technology capability/modern-workplace: 1.69 capability/endpoint-security: 2.73 capability/security: 1.91 vendor/igel: 3.03 annotations: source: src/content/solutions/en/igel.md route: /en/solutions/igel/ schema: /nerd/schema/solutions.json markdown: /en/solutions/igel.mdspec: title: IGEL tags: [modern-workplace, endpoint-security, security] vendors: [igel] summary: >- The endpoint half of the virtual workplace. IGEL fits when the desktop runs somewhere else. photoNeed: >- An IGEL endpoint in place: a UD Pocket in a laptop, or a thin client at a working desk stub: false draft: false kind: vendor addon: false sourceNote: >- soultec.ch/solutions/igel, read 2026-08-30, for the partnership; igel.com and kb.igel.com, same day, for the platform and the editions vendorName: IGEL Technology status: current practice: >- Draft, not yet reviewed. We come at IGEL from the virtualization side. The estate usually already has Horizon or AVD, and the question is what people sit in front of. That is also why the peripheral inventory is the first thing we ask for and the security case is the second. practiceReview: true sections: - heading:

The partnership

body: | Our team has specialised in virtualization and digital workspace technology for years, and IGEL is what completes that at the other end of the wire. We build the desktops, and IGEL covers the endpoints. - heading:

What IGEL is built for

body: | In a production estate what counts is stability, security, central management and whether the person at the desk notices any of it. IGEL is built for those four, and has been building secure endpoint software since 2001. - heading:

What we do with it

body: | Planning, implementation and the tuning afterwards. Our engineers stay current on IGEL and on modern workplace technology generally. - heading:

Where it stops

body: | IGEL only fits when the real environment runs somewhere else. Anything that has to execute locally will not run on it, and an inventory of those belongs at the start of a project.status: corpus: 315 services: - {ref: services/modern-workplace, score: 0.70} - {ref: services/managed-security, score: 0.43} - {ref: services/security, score: 0.37} - {ref: services/academy, score: 0.30} experts: - {ref: experts/valentina-cicmak, score: 0.51} - {ref: experts/michael-steg, score: 0.39} - {ref: experts/oliver-erismann, score: 0.21} neighbours: - {ref: solutions/igel/addon/igel-contextual-access, score: 1.00} - {ref: solutions/igel/addon/90meter, score: 0.81} - {ref: solutions/igel/igel-os, score: 0.79} search: /en/search.json

{ "apiVersion": "soultec.ch/v1", "kind": "Solution", "metadata": { "name": "igel", "locale": "en", "labels": { "vendor": "IGEL Technology", "capability/modern-workplace": 1.69, "capability/endpoint-security": 2.73, "capability/security": 1.91, "vendor/igel": 3.03 }, "annotations": { "source": "src/content/solutions/en/igel.md", "route": "/en/solutions/igel/", "schema": "/nerd/schema/solutions.json", "markdown": "/en/solutions/igel.md" } }, "spec": { "title": "IGEL", "tags": [ "modern-workplace", "endpoint-security", "security" ], "vendors": [ "igel" ], "summary": "The endpoint half of the virtual workplace. IGEL fits when the desktop runs somewhere else.", "photoNeed": "An IGEL endpoint in place: a UD Pocket in a laptop, or a thin client at a working desk", "stub": false, "draft": false, "kind": "vendor", "addon": false, "sourceNote": "soultec.ch/solutions/igel, read 2026-08-30, for the partnership; igel.com and kb.igel.com, same day, for the platform and the editions", "vendorName": "IGEL Technology", "status": "current", "practice": "Draft, not yet reviewed. We come at IGEL from the virtualization side. The estate usually already has Horizon or AVD, and the question is what people sit in front of. That is also why the peripheral inventory is the first thing we ask for and the security case is the second.\n", "practiceReview": true, "sections": [ { "heading": "

The partnership

", "body": "Our team has specialised in virtualization and digital workspace technology for years, and\nIGEL is what completes that at the other end of the wire. We build the desktops, and IGEL\ncovers the endpoints." }, { "heading": "

What IGEL is built for

", "body": "In a production estate what counts is stability, security, central management and whether\nthe person at the desk notices any of it. IGEL is built for those four, and has been\nbuilding secure endpoint software since 2001." }, { "heading": "

What we do with it

", "body": "Planning, implementation and the tuning afterwards. Our engineers stay current on IGEL and\non modern workplace technology generally." }, { "heading": "

Where it stops

", "body": "IGEL only fits when the real environment runs somewhere else. Anything that has to execute\nlocally will not run on it, and an inventory of those belongs at the start of a project." } ] }, "status": { "corpus": 315, "services": [ { "ref": "services/modern-workplace", "score": "0.70" }, { "ref": "services/managed-security", "score": "0.43" }, { "ref": "services/security", "score": "0.37" }, { "ref": "services/academy", "score": "0.30" } ], "experts": [ { "ref": "experts/valentina-cicmak", "score": "0.51" }, { "ref": "experts/michael-steg", "score": "0.39" }, { "ref": "experts/oliver-erismann", "score": "0.21" } ], "neighbours": [ { "ref": "solutions/igel/addon/igel-contextual-access", "score": "1.00" }, { "ref": "solutions/igel/addon/90meter", "score": "0.81" }, { "ref": "solutions/igel/igel-os", "score": "0.79" } ], "search": "/en/search.json" }}

apiVersion = "soultec.ch/v1"kind = "Solution"[metadata]name = "igel"locale = "en"[metadata.labels]vendor = "IGEL Technology""capability/modern-workplace" = 1.69"capability/endpoint-security" = 2.73"capability/security" = 1.91"vendor/igel" = 3.03[metadata.annotations]source = "src/content/solutions/en/igel.md"route = "/en/solutions/igel/"schema = "/nerd/schema/solutions.json"markdown = "/en/solutions/igel.md"[spec]title = "IGEL"tags = ["modern-workplace", "endpoint-security", "security"]vendors = ["igel"]summary = "The endpoint half of the virtual workplace. IGEL fits when the desktop runs somewhere else."photoNeed = "An IGEL endpoint in place: a UD Pocket in a laptop, or a thin client at a working desk"stub = falsedraft = falsekind = "vendor"addon = falsesourceNote = "soultec.ch/solutions/igel, read 2026-08-30, for the partnership; igel.com and kb.igel.com, same day, for the platform and the editions"vendorName = "IGEL Technology"status = "current"practice = '''Draft, not yet reviewed. We come at IGEL from the virtualization side. The estate usually already has Horizon or AVD, and the question is what people sit in front of. That is also why the peripheral inventory is the first thing we ask for and the security case is the second.'''practiceReview = true[[spec.sections]]heading = "

The partnership

"body = '''Our team has specialised in virtualization and digital workspace technology for years, andIGEL is what completes that at the other end of the wire. We build the desktops, and IGELcovers the endpoints.'''[[spec.sections]]heading = "

What IGEL is built for

"body = '''In a production estate what counts is stability, security, central management and whetherthe person at the desk notices any of it. IGEL is built for those four, and has beenbuilding secure endpoint software since 2001.'''[[spec.sections]]heading = "

What we do with it

"body = '''Planning, implementation and the tuning afterwards. Our engineers stay current on IGEL andon modern workplace technology generally.'''[[spec.sections]]heading = "

Where it stops

"body = '''IGEL only fits when the real environment runs somewhere else. Anything that has to executelocally will not run on it, and an inventory of those belongs at the start of a project.'''[status]corpus = 315search = "/en/search.json"[[status.services]]ref = "services/modern-workplace"score = "0.70"[[status.services]]ref = "services/managed-security"score = "0.43"[[status.services]]ref = "services/security"score = "0.37"[[status.services]]ref = "services/academy"score = "0.30"[[status.experts]]ref = "experts/valentina-cicmak"score = "0.51"[[status.experts]]ref = "experts/michael-steg"score = "0.39"[[status.experts]]ref = "experts/oliver-erismann"score = "0.21"[[status.neighbours]]ref = "solutions/igel/addon/igel-contextual-access"score = "1.00"[[status.neighbours]]ref = "solutions/igel/addon/90meter"score = "0.81"[[status.neighbours]]ref = "solutions/igel/igel-os"score = "0.79"

<?xml version="1.0" encoding="UTF-8"?><manifest kind="Solution"> <apiVersion>soultec.ch/v1</apiVersion> <metadata> <name>igel</name> <locale>en</locale> <labels> <vendor>IGEL Technology</vendor> <entry key="capability/modern-workplace">1.69</entry> <entry key="capability/endpoint-security">2.73</entry> <entry key="capability/security">1.91</entry> <entry key="vendor/igel">3.03</entry> </labels> <annotations> <source>src/content/solutions/en/igel.md</source> <route>/en/solutions/igel/</route> <schema>/nerd/schema/solutions.json</schema> <markdown>/en/solutions/igel.md</markdown> </annotations> </metadata> <spec> <title>IGEL</title> <tags> <item>modern-workplace</item> <item>endpoint-security</item> <item>security</item> </tags> <vendors> <item>igel</item> </vendors> <summary>The endpoint half of the virtual workplace. IGEL fits when the desktop runs somewhere else.</summary> <photoNeed>An IGEL endpoint in place: a UD Pocket in a laptop, or a thin client at a working desk</photoNeed> <stub>false</stub> <draft>false</draft> <kind>vendor</kind> <addon>false</addon> <sourceNote>soultec.ch/solutions/igel, read 2026-08-30, for the partnership; igel.com and kb.igel.com, same day, for the platform and the editions</sourceNote> <vendorName>IGEL Technology</vendorName> <status>current</status> <practice>Draft, not yet reviewed. We come at IGEL from the virtualization side. The estate usually already has Horizon or AVD, and the question is what people sit in front of. That is also why the peripheral inventory is the first thing we ask for and the security case is the second. </practice> <practiceReview>true</practiceReview> <sections> <section> <heading>

The partnership

</heading> <body>Our team has specialised in virtualization and digital workspace technology for years, andIGEL is what completes that at the other end of the wire. We build the desktops, and IGELcovers the endpoints. </body> </section> <section> <heading>

What IGEL is built for

</heading> <body>In a production estate what counts is stability, security, central management and whetherthe person at the desk notices any of it. IGEL is built for those four, and has beenbuilding secure endpoint software since 2001. </body> </section> <section> <heading>

What we do with it

</heading> <body>Planning, implementation and the tuning afterwards. Our engineers stay current on IGEL andon modern workplace technology generally. </body> </section> <section> <heading>

Where it stops

</heading> <body>IGEL only fits when the real environment runs somewhere else. Anything that has to executelocally will not run on it, and an inventory of those belongs at the start of a project. </body> </section> </sections> </spec> <status> <corpus>315</corpus> <services> <item> <ref>services/modern-workplace</ref> <score>0.70</score> </item> <item> <ref>services/managed-security</ref> <score>0.43</score> </item> <item> <ref>services/security</ref> <score>0.37</score> </item> <item> <ref>services/academy</ref> <score>0.30</score> </item> </services> <experts> <item> <ref>experts/valentina-cicmak</ref> <score>0.51</score> </item> <item> <ref>experts/michael-steg</ref> <score>0.39</score> </item> <item> <ref>experts/oliver-erismann</ref> <score>0.21</score> </item> </experts> <neighbours> <item> <ref>solutions/igel/addon/igel-contextual-access</ref> <score>1.00</score> </item> <item> <ref>solutions/igel/addon/90meter</ref> <score>0.81</score> </item> <item> <ref>solutions/igel/igel-os</ref> <score>0.79</score> </item> </neighbours> <search>/en/search.json</search> </status></manifest>

# Code generated by the soultec.ch build. DO NOT EDIT.import jsonPAGE = { "apiVersion": "soultec.ch/v1", "kind": "Solution", "metadata": { "name": "igel", "locale": "en", "labels": { "vendor": "IGEL Technology", "capability/modern-workplace": 1.69, "capability/endpoint-security": 2.73, "capability/security": 1.91, "vendor/igel": 3.03, }, "annotations": { "source": "src/content/solutions/en/igel.md", "route": "/en/solutions/igel/", "schema": "/nerd/schema/solutions.json", "markdown": "/en/solutions/igel.md", }, }, "spec": { "title": "IGEL", "tags": ["modern-workplace", "endpoint-security", "security"], "vendors": ["igel"], "summary": "The endpoint half of the virtual workplace. IGEL fits when the desktop runs somewhere else.", "photoNeed": "An IGEL endpoint in place: a UD Pocket in a laptop, or a thin client at a working desk", "stub": False, "draft": False, "kind": "vendor", "addon": False, "sourceNote": "soultec.ch/solutions/igel, read 2026-08-30, for the partnership; igel.com and kb.igel.com, same day, for the platform and the editions", "vendorName": "IGEL Technology", "status": "current", "practice": ( "Draft, not yet reviewed. We come at IGEL from the virtualization side. The estate usually already has Horizon or AVD, and the question is what people sit in front of. That is also why the peripheral inventory is the first thing we ask for and the security case is the second.\n" ), "practiceReview": True, "sections": [ { "heading": "

The partnership

", "body": ( "Our team has specialised in virtualization and digital workspace technology for years, and\n" "IGEL is what completes that at the other end of the wire. We build the desktops, and IGEL\n" "covers the endpoints." ), }, { "heading": "

What IGEL is built for

", "body": ( "In a production estate what counts is stability, security, central management and whether\n" "the person at the desk notices any of it. IGEL is built for those four, and has been\n" "building secure endpoint software since 2001." ), }, { "heading": "

What we do with it

", "body": ( "Planning, implementation and the tuning afterwards. Our engineers stay current on IGEL and\n" "on modern workplace technology generally." ), }, { "heading": "

Where it stops

", "body": ( "IGEL only fits when the real environment runs somewhere else. Anything that has to execute\n" "locally will not run on it, and an inventory of those belongs at the start of a project." ), }, ], }, "status": { "corpus": 315, "services": [ { "ref": "services/modern-workplace", "score": "0.70", }, { "ref": "services/managed-security", "score": "0.43", }, { "ref": "services/security", "score": "0.37", }, { "ref": "services/academy", "score": "0.30", }, ], "experts": [ { "ref": "experts/valentina-cicmak", "score": "0.51", }, { "ref": "experts/michael-steg", "score": "0.39", }, { "ref": "experts/oliver-erismann", "score": "0.21", }, ], "neighbours": [ { "ref": "solutions/igel/addon/igel-contextual-access", "score": "1.00", }, { "ref": "solutions/igel/addon/90meter", "score": "0.81", }, { "ref": "solutions/igel/igel-os", "score": "0.79", }, ], "search": "/en/search.json", },}if __name__ == "__main__": print(json.dumps(PAGE, indent=2, ensure_ascii=False))

# Code generated by the soultec.ch build. DO NOT EDIT.$Page = [ordered]@{ apiVersion = 'soultec.ch/v1' kind = 'Solution' metadata = [ordered]@{ name = 'igel' locale = 'en' labels = [ordered]@{ vendor = 'IGEL Technology' 'capability/modern-workplace' = 1.69 'capability/endpoint-security' = 2.73 'capability/security' = 1.91 'vendor/igel' = 3.03 } annotations = [ordered]@{ source = 'src/content/solutions/en/igel.md' route = '/en/solutions/igel/' schema = '/nerd/schema/solutions.json' markdown = '/en/solutions/igel.md' } } spec = [ordered]@{ title = 'IGEL' tags = @('modern-workplace', 'endpoint-security', 'security') vendors = @('igel') summary = 'The endpoint half of the virtual workplace. IGEL fits when the desktop runs somewhere else.' photoNeed = 'An IGEL endpoint in place: a UD Pocket in a laptop, or a thin client at a working desk' stub = $false draft = $false kind = 'vendor' addon = $false sourceNote = 'soultec.ch/solutions/igel, read 2026-08-30, for the partnership; igel.com and kb.igel.com, same day, for the platform and the editions' vendorName = 'IGEL Technology' status = 'current' practice = @'Draft, not yet reviewed. We come at IGEL from the virtualization side. The estate usually already has Horizon or AVD, and the question is what people sit in front of. That is also why the peripheral inventory is the first thing we ask for and the security case is the second.'@ practiceReview = $true sections = @( [ordered]@{ heading = '

The partnership

' body = @'Our team has specialised in virtualization and digital workspace technology for years, andIGEL is what completes that at the other end of the wire. We build the desktops, and IGELcovers the endpoints.'@ } [ordered]@{ heading = '

What IGEL is built for

' body = @'In a production estate what counts is stability, security, central management and whetherthe person at the desk notices any of it. IGEL is built for those four, and has beenbuilding secure endpoint software since 2001.'@ } [ordered]@{ heading = '

What we do with it

' body = @'Planning, implementation and the tuning afterwards. Our engineers stay current on IGEL andon modern workplace technology generally.'@ } [ordered]@{ heading = '

Where it stops

' body = @'IGEL only fits when the real environment runs somewhere else. Anything that has to executelocally will not run on it, and an inventory of those belongs at the start of a project.'@ } ) } status = [ordered]@{ corpus = 315 services = @( [ordered]@{ ref = 'services/modern-workplace' score = '0.70' } [ordered]@{ ref = 'services/managed-security' score = '0.43' } [ordered]@{ ref = 'services/security' score = '0.37' } [ordered]@{ ref = 'services/academy' score = '0.30' } ) experts = @( [ordered]@{ ref = 'experts/valentina-cicmak' score = '0.51' } [ordered]@{ ref = 'experts/michael-steg' score = '0.39' } [ordered]@{ ref = 'experts/oliver-erismann' score = '0.21' } ) neighbours = @( [ordered]@{ ref = 'solutions/igel/addon/igel-contextual-access' score = '1.00' } [ordered]@{ ref = 'solutions/igel/addon/90meter' score = '0.81' } [ordered]@{ ref = 'solutions/igel/igel-os' score = '0.79' } ) search = '/en/search.json' }}$Page | ConvertTo-Json -Depth 32

// Code generated by the soultec.ch build. DO NOT EDIT.package mainimport ( "encoding/json" "os")var page = map[string]any{ "apiVersion": "soultec.ch/v1", "kind": "Solution", "metadata": map[string]any{ "name": "igel", "locale": "en", "labels": map[string]any{ "vendor": "IGEL Technology", "capability/modern-workplace": 1.69, "capability/endpoint-security": 2.73, "capability/security": 1.91, "vendor/igel": 3.03, }, "annotations": map[string]any{ "source": "src/content/solutions/en/igel.md", "route": "/en/solutions/igel/", "schema": "/nerd/schema/solutions.json", "markdown": "/en/solutions/igel.md", }, }, "spec": map[string]any{ "title": "IGEL", "tags": []any{"modern-workplace", "endpoint-security", "security"}, "vendors": []any{"igel"}, "summary": "The endpoint half of the virtual workplace. IGEL fits when the desktop runs somewhere else.", "photoNeed": "An IGEL endpoint in place: a UD Pocket in a laptop, or a thin client at a working desk", "stub": false, "draft": false, "kind": "vendor", "addon": false, "sourceNote": "soultec.ch/solutions/igel, read 2026-08-30, for the partnership; igel.com and kb.igel.com, same day, for the platform and the editions", "vendorName": "IGEL Technology", "status": "current", "practice": "Draft, not yet reviewed. We come at IGEL from the virtualization side. The estate usually already has Horizon or AVD, and the question is what people sit in front of. That is also why the peripheral inventory is the first thing we ask for and the security case is the second.\n", "practiceReview": true, "sections": []any{ map[string]any{ "heading": "

The partnership

", "body": "Our team has specialised in virtualization and digital workspace technology for years, and\n" + "IGEL is what completes that at the other end of the wire. We build the desktops, and IGEL\n" + "covers the endpoints.", }, map[string]any{ "heading": "

What IGEL is built for

", "body": "In a production estate what counts is stability, security, central management and whether\n" + "the person at the desk notices any of it. IGEL is built for those four, and has been\n" + "building secure endpoint software since 2001.", }, map[string]any{ "heading": "

What we do with it

", "body": "Planning, implementation and the tuning afterwards. Our engineers stay current on IGEL and\n" + "on modern workplace technology generally.", }, map[string]any{ "heading": "

Where it stops

", "body": "IGEL only fits when the real environment runs somewhere else. Anything that has to execute\n" + "locally will not run on it, and an inventory of those belongs at the start of a project.", }, }, }, "status": map[string]any{ "corpus": 315, "services": []any{ map[string]any{ "ref": "services/modern-workplace", "score": "0.70", }, map[string]any{ "ref": "services/managed-security", "score": "0.43", }, map[string]any{ "ref": "services/security", "score": "0.37", }, map[string]any{ "ref": "services/academy", "score": "0.30", }, }, "experts": []any{ map[string]any{ "ref": "experts/valentina-cicmak", "score": "0.51", }, map[string]any{ "ref": "experts/michael-steg", "score": "0.39", }, map[string]any{ "ref": "experts/oliver-erismann", "score": "0.21", }, }, "neighbours": []any{ map[string]any{ "ref": "solutions/igel/addon/igel-contextual-access", "score": "1.00", }, map[string]any{ "ref": "solutions/igel/addon/90meter", "score": "0.81", }, map[string]any{ "ref": "solutions/igel/igel-os", "score": "0.79", }, }, "search": "/en/search.json", },}func main() { enc := json.NewEncoder(os.Stdout) enc.SetEscapeHTML(false) enc.SetIndent("", " ") if err := enc.Encode(page); err != nil { os.Exit(1) }}

// Code generated by the soultec.ch build. DO NOT EDIT.const page = { apiVersion: "soultec.ch/v1", kind: "Solution", metadata: { name: "igel", locale: "en", labels: { vendor: "IGEL Technology", "capability/modern-workplace": 1.69, "capability/endpoint-security": 2.73, "capability/security": 1.91, "vendor/igel": 3.03, }, annotations: { source: "src/content/solutions/en/igel.md", route: "/en/solutions/igel/", schema: "/nerd/schema/solutions.json", markdown: "/en/solutions/igel.md", }, }, spec: { title: "IGEL", tags: ["modern-workplace", "endpoint-security", "security"], vendors: ["igel"], summary: "The endpoint half of the virtual workplace. IGEL fits when the desktop runs somewhere else.", photoNeed: "An IGEL endpoint in place: a UD Pocket in a laptop, or a thin client at a working desk", stub: false, draft: false, kind: "vendor", addon: false, sourceNote: "soultec.ch/solutions/igel, read 2026-08-30, for the partnership; igel.com and kb.igel.com, same day, for the platform and the editions", vendorName: "IGEL Technology", status: "current", practice: "Draft, not yet reviewed. We come at IGEL from the virtualization side. The estate usually already has Horizon or AVD, and the question is what people sit in front of. That is also why the peripheral inventory is the first thing we ask for and the security case is the second.\n", practiceReview: true, sections: [ { heading: "

The partnership

", body: "Our team has specialised in virtualization and digital workspace technology for years, and\n" + "IGEL is what completes that at the other end of the wire. We build the desktops, and IGEL\n" + "covers the endpoints.", }, { heading: "

What IGEL is built for

", body: "In a production estate what counts is stability, security, central management and whether\n" + "the person at the desk notices any of it. IGEL is built for those four, and has been\n" + "building secure endpoint software since 2001.", }, { heading: "

What we do with it

", body: "Planning, implementation and the tuning afterwards. Our engineers stay current on IGEL and\n" + "on modern workplace technology generally.", }, { heading: "

Where it stops

", body: "IGEL only fits when the real environment runs somewhere else. Anything that has to execute\n" + "locally will not run on it, and an inventory of those belongs at the start of a project.", }, ], }, status: { corpus: 315, services: [ { ref: "services/modern-workplace", score: "0.70", }, { ref: "services/managed-security", score: "0.43", }, { ref: "services/security", score: "0.37", }, { ref: "services/academy", score: "0.30", }, ], experts: [ { ref: "experts/valentina-cicmak", score: "0.51", }, { ref: "experts/michael-steg", score: "0.39", }, { ref: "experts/oliver-erismann", score: "0.21", }, ], neighbours: [ { ref: "solutions/igel/addon/igel-contextual-access", score: "1.00", }, { ref: "solutions/igel/addon/90meter", score: "0.81", }, { ref: "solutions/igel/igel-os", score: "0.79", }, ], search: "/en/search.json", },};console.log(JSON.stringify(page, null, 2));

# 74 lines · YAML · validated at build# 111 lines · JSON · validated at build# 112 lines · TOML · validated at build# 128 lines · XML · validated at build# 127 lines · Python · read back at build, equals the JSON record# 125 lines · PowerShell · read back at build, equals the JSON record# 129 lines · Go · read back at build, equals the JSON record# 114 lines · JavaScript · read back at build, equals the JSON record · served at /en/solutions/igel.md

Solution · IGEL

IGEL

The vendor calls it: IGEL Technology

The endpoint half of the virtual workplace. IGEL fits when the desktop runs somewhere else.

Topics Modern Workplace 1.69 Endpoint Security 2.73 Security 1.91

Vendors IGEL 3.03

04Services

03Capabilities

315Corpus

photograph wantedAn IGEL endpoint in place: a UD Pocket in a laptop, or a thin client at a working desk

The partnership

Our team has specialised in virtualization and digital workspace technology for years, and IGEL is what completes that at the other end of the wire. We build the desktops, and IGEL covers the endpoints.

What IGEL is built for

In a production estate what counts is stability, security, central management and whether the person at the desk notices any of it. IGEL is built for those four, and has been building secure endpoint software since 2001.

What we do with it

Planning, implementation and the tuning afterwards. Our engineers stay current on IGEL and on modern workplace technology generally.

Where it stops

IGEL only fits when the real environment runs somewhere else. Anything that has to execute locally will not run on it, and an inventory of those belongs at the start of a project.

What we do with it

Draft, unreviewed

Draft, not yet reviewed. We come at IGEL from the virtualization side. The estate usually already has Horizon or AVD, and the question is what people sit in front of. That is also why the peripheral inventory is the first thing we ask for and the security case is the second.

This paragraph is a draft and nobody at soulTec has confirmed it yet. Everything above it describes the product and is checkable against the vendor.

Products 13, 4 written

IGEL OS

Platform

A read-only Linux as the endpoint operating system. Turns existing hardware into a managed access point and extends how long it stays useful.

Modern WorkplaceEndpoint Security

IGEL Cloud Gateway StandardEnterpriseHealthcareGovernmentBC&DR Modern WorkplaceNetworkManaged Services
Managed Containers Add-on EnterpriseHealthcareGovernmentBC&DR ContainersModern Workplace
Managed Hypervisor Add-on EnterpriseHealthcareGovernmentBC&DR VirtualizationModern Workplace
UD Pocket Add-on StandardEnterpriseHealthcareGovernmentBC&DR Modern WorkplaceBackup and Recovery

Add-ons

90Meter Add-on GovernmentBC&DR SecurityEndpoint Security
Advanced Device Redirection Add-on EssentialStandardEnterpriseHealthcareGovernmentBC&DR Modern WorkplaceVirtualization
Contextual Access Add-on EnterpriseHealthcareGovernmentBC&DR SecurityEndpoint SecurityModern Workplace
Smart Login Add-on StandardEnterpriseHealthcareGovernmentBC&DR SecurityModern Workplace
UMS as a Service Add-on EnterpriseHealthcareGovernmentBC&DR Managed ServicesModern WorkplaceCloud

A name without a link is real but not written yet. It comes from soultec.ch or from the vendor’s own product material.

Who works with it

Valentina Cicmak

System Engineer

Endpoint SecurityModern Workplace

0.51

Michael Steg

Senior Solution Architect

SecurityModern Workplace

0.39

Oliver Erismann

Senior System Engineer

Endpoint SecurityModern Workplace

0.21

Do you work with this? Take a look at our open roles.

The partnership

What IGEL is built for

What we do with it

Where it stops

The partnership

What IGEL is built for

What we do with it

Where it stops

The partnership

What IGEL is built for

What we do with it

Where it stops

The partnership

What IGEL is built for

What we do with it

Where it stops

The partnership

What IGEL is built for

What we do with it

Where it stops

The partnership

What IGEL is built for

What we do with it

Where it stops

The partnership

What IGEL is built for

What we do with it

Where it stops

The partnership

What IGEL is built for

What we do with it

Where it stops

IGEL

The partnership

What IGEL is built for

What we do with it

Where it stops

What we do with it

Products 13, 4 written

IGEL OS

App Portal

Onboarding Service

Universal Management Suite UMS

Add-ons

Who works with it

Valentina Cicmak

Michael Steg

Oliver Erismann