build 6ddc7a35 | content blog-content@417154f · 338 posts | profiles 32 · corpus 315 | ● 0 skipped | format run

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

apiVersion: soultec.ch/v1kind: Solutionmetadata: name: igel/igel-app-portal locale: en labels: vendor: IGEL App Portal capability/modern-workplace: 1.69 capability/automation: 1.81 vendor/igel: 3.03 annotations: source: src/content/solutions/en/igel/igel-app-portal.md route: /en/solutions/igel/igel-app-portal/ schema: /nerd/schema/solutions.json markdown: /en/solutions/igel/igel-app-portal.mdspec: title: App Portal tags: [modern-workplace, automation] vendors: [igel] summary: >- IGEL OS 12 ships with no applications. Everything a person uses arrives from here as a package, and updates without touching the operating system. 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: product addon: false sourceNote: >- soultec.ch/solutions/igel, read 2026-08-30; igel.com product navigation, same day vendorName: IGEL App Portal status: current sections: - heading:

What it is

body: | The App Portal is where the applications come from. IGEL OS 12's base image deliberately contains none, so the Citrix client, the Omnissa Horizon client, the Azure Virtual Desktop client and the browsers are all selected in the portal and pushed to devices or device groups from there. It is part of the IGEL cloud services. - heading:

Applications as containers

body: | Applications are delivered as containers, managed apart from the operating system. So a client update is a package of its own and no longer has to be scheduled against an OS release. In IGEL OS 11 the VDI client version is tied to the OS release. - heading:

What to watch

body: | An estate with no route to the internet does not reach the portal. IGEL's answer is the distributed app repository, where devices pull packages from a local server instead, and that is an Enterprise-licence feature. There is also peer update, where a device pulls from another device on the same network, and that one is in every edition. Which of the two you need depends on how the network is separated.status: corpus: 315 experts: - {ref: experts/michael-steg, score: 0.40} - {ref: experts/valentina-cicmak, score: 0.38} neighbours: - {ref: solutions/igel, relation: parent} - {ref: solutions/microsoft/easylife-365-collaboration, score: 0.70} - {ref: solutions/omnissa/omnissa-freestyle-orchestrator, score: 0.70} - {ref: solutions/igel/igel-onboarding-service, score: 0.70} search: /en/search.json
{ "apiVersion": "soultec.ch/v1", "kind": "Solution", "metadata": { "name": "igel/igel-app-portal", "locale": "en", "labels": { "vendor": "IGEL App Portal", "capability/modern-workplace": 1.69, "capability/automation": 1.81, "vendor/igel": 3.03 }, "annotations": { "source": "src/content/solutions/en/igel/igel-app-portal.md", "route": "/en/solutions/igel/igel-app-portal/", "schema": "/nerd/schema/solutions.json", "markdown": "/en/solutions/igel/igel-app-portal.md" } }, "spec": { "title": "App Portal", "tags": [ "modern-workplace", "automation" ], "vendors": [ "igel" ], "summary": "IGEL OS 12 ships with no applications. Everything a person uses arrives from here as a package, and updates without touching the operating system.", "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": "product", "addon": false, "sourceNote": "soultec.ch/solutions/igel, read 2026-08-30; igel.com product navigation, same day", "vendorName": "IGEL App Portal", "status": "current", "sections": [ { "heading": "

What it is

",
"body": "The App Portal is where the applications come from. IGEL OS 12's base image deliberately\ncontains none, so the Citrix client, the Omnissa Horizon client, the Azure Virtual Desktop\nclient and the browsers are all selected in the portal and pushed to devices or device\ngroups from there.\n\nIt is part of the IGEL cloud services." }, { "heading": "

Applications as containers

",
"body": "Applications are delivered as containers, managed apart from the operating system. So a\nclient update is a package of its own and no longer has to be scheduled against an OS\nrelease.\n\nIn IGEL OS 11 the VDI client version is tied to the OS release." }, { "heading": "

What to watch

",
"body": "An estate with no route to the internet does not reach the portal. IGEL's answer is the\ndistributed app repository, where devices pull packages from a local server instead, and\nthat is an Enterprise-licence feature. There is also peer update, where a device pulls from\nanother device on the same network, and that one is in every edition.\n\nWhich of the two you need depends on how the network is separated." } ] }, "status": { "corpus": 315, "experts": [ { "ref": "experts/michael-steg", "score": "0.40" }, { "ref": "experts/valentina-cicmak", "score": "0.38" } ], "neighbours": [ { "ref": "solutions/igel", "relation": "parent" }, { "ref": "solutions/microsoft/easylife-365-collaboration", "score": "0.70" }, { "ref": "solutions/omnissa/omnissa-freestyle-orchestrator", "score": "0.70" }, { "ref": "solutions/igel/igel-onboarding-service", "score": "0.70" } ], "search": "/en/search.json" }}
apiVersion = "soultec.ch/v1"kind = "Solution"[metadata]name = "igel/igel-app-portal"locale = "en"[metadata.labels]vendor = "IGEL App Portal""capability/modern-workplace" = 1.69"capability/automation" = 1.81"vendor/igel" = 3.03[metadata.annotations]source = "src/content/solutions/en/igel/igel-app-portal.md"route = "/en/solutions/igel/igel-app-portal/"schema = "/nerd/schema/solutions.json"markdown = "/en/solutions/igel/igel-app-portal.md"[spec]title = "App Portal"tags = ["modern-workplace", "automation"]vendors = ["igel"]summary = "IGEL OS 12 ships with no applications. Everything a person uses arrives from here as a package, and updates without touching the operating system."photoNeed = "An IGEL endpoint in place: a UD Pocket in a laptop, or a thin client at a working desk"stub = falsedraft = falsekind = "product"addon = falsesourceNote = "soultec.ch/solutions/igel, read 2026-08-30; igel.com product navigation, same day"vendorName = "IGEL App Portal"status = "current"[[spec.sections]]heading = "

What it is

"
body = '''The App Portal is where the applications come from. IGEL OS 12's base image deliberatelycontains none, so the Citrix client, the Omnissa Horizon client, the Azure Virtual Desktopclient and the browsers are all selected in the portal and pushed to devices or devicegroups from there.It is part of the IGEL cloud services.'''[[spec.sections]]heading = "

Applications as containers

"
body = '''Applications are delivered as containers, managed apart from the operating system. So aclient update is a package of its own and no longer has to be scheduled against an OSrelease.In IGEL OS 11 the VDI client version is tied to the OS release.'''[[spec.sections]]heading = "

What to watch

"
body = '''An estate with no route to the internet does not reach the portal. IGEL's answer is thedistributed app repository, where devices pull packages from a local server instead, andthat is an Enterprise-licence feature. There is also peer update, where a device pulls fromanother device on the same network, and that one is in every edition.Which of the two you need depends on how the network is separated.'''[status]corpus = 315search = "/en/search.json"[[status.experts]]ref = "experts/michael-steg"score = "0.40"[[status.experts]]ref = "experts/valentina-cicmak"score = "0.38"[[status.neighbours]]ref = "solutions/igel"relation = "parent"[[status.neighbours]]ref = "solutions/microsoft/easylife-365-collaboration"score = "0.70"[[status.neighbours]]ref = "solutions/omnissa/omnissa-freestyle-orchestrator"score = "0.70"[[status.neighbours]]ref = "solutions/igel/igel-onboarding-service"score = "0.70"
<?xml version="1.0" encoding="UTF-8"?><manifest kind="Solution"> <apiVersion>soultec.ch/v1</apiVersion> <metadata> <name>igel/igel-app-portal</name> <locale>en</locale> <labels> <vendor>IGEL App Portal</vendor> <entry key="capability/modern-workplace">1.69</entry> <entry key="capability/automation">1.81</entry> <entry key="vendor/igel">3.03</entry> </labels> <annotations> <source>src/content/solutions/en/igel/igel-app-portal.md</source> <route>/en/solutions/igel/igel-app-portal/</route> <schema>/nerd/schema/solutions.json</schema> <markdown>/en/solutions/igel/igel-app-portal.md</markdown> </annotations> </metadata> <spec> <title>App Portal</title> <tags> <item>modern-workplace</item> <item>automation</item> </tags> <vendors> <item>igel</item> </vendors> <summary>IGEL OS 12 ships with no applications. Everything a person uses arrives from here as a package, and updates without touching the operating system.</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>product</kind> <addon>false</addon> <sourceNote>soultec.ch/solutions/igel, read 2026-08-30; igel.com product navigation, same day</sourceNote> <vendorName>IGEL App Portal</vendorName> <status>current</status> <sections> <section> <heading>

What it is

</heading>
<body>The App Portal is where the applications come from. IGEL OS 12's base image deliberatelycontains none, so the Citrix client, the Omnissa Horizon client, the Azure Virtual Desktopclient and the browsers are all selected in the portal and pushed to devices or devicegroups from there.It is part of the IGEL cloud services. </body> </section> <section> <heading>

Applications as containers

</heading>
<body>Applications are delivered as containers, managed apart from the operating system. So aclient update is a package of its own and no longer has to be scheduled against an OSrelease.In IGEL OS 11 the VDI client version is tied to the OS release. </body> </section> <section> <heading>

What to watch

</heading>
<body>An estate with no route to the internet does not reach the portal. IGEL's answer is thedistributed app repository, where devices pull packages from a local server instead, andthat is an Enterprise-licence feature. There is also peer update, where a device pulls fromanother device on the same network, and that one is in every edition.Which of the two you need depends on how the network is separated. </body> </section> </sections> </spec> <status> <corpus>315</corpus> <experts> <item> <ref>experts/michael-steg</ref> <score>0.40</score> </item> <item> <ref>experts/valentina-cicmak</ref> <score>0.38</score> </item> </experts> <neighbours> <item> <ref>solutions/igel</ref> <relation>parent</relation> </item> <item> <ref>solutions/microsoft/easylife-365-collaboration</ref> <score>0.70</score> </item> <item> <ref>solutions/omnissa/omnissa-freestyle-orchestrator</ref> <score>0.70</score> </item> <item> <ref>solutions/igel/igel-onboarding-service</ref> <score>0.70</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/igel-app-portal", "locale": "en", "labels": { "vendor": "IGEL App Portal", "capability/modern-workplace": 1.69, "capability/automation": 1.81, "vendor/igel": 3.03, }, "annotations": { "source": "src/content/solutions/en/igel/igel-app-portal.md", "route": "/en/solutions/igel/igel-app-portal/", "schema": "/nerd/schema/solutions.json", "markdown": "/en/solutions/igel/igel-app-portal.md", }, }, "spec": { "title": "App Portal", "tags": ["modern-workplace", "automation"], "vendors": ["igel"], "summary": "IGEL OS 12 ships with no applications. Everything a person uses arrives from here as a package, and updates without touching the operating system.", "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": "product", "addon": False, "sourceNote": "soultec.ch/solutions/igel, read 2026-08-30; igel.com product navigation, same day", "vendorName": "IGEL App Portal", "status": "current", "sections": [ { "heading": "

What it is

",
"body": ( "The App Portal is where the applications come from. IGEL OS 12's base image deliberately\n" "contains none, so the Citrix client, the Omnissa Horizon client, the Azure Virtual Desktop\n" "client and the browsers are all selected in the portal and pushed to devices or device\n" "groups from there.\n" "\n" "It is part of the IGEL cloud services." ), }, { "heading": "

Applications as containers

",
"body": ( "Applications are delivered as containers, managed apart from the operating system. So a\n" "client update is a package of its own and no longer has to be scheduled against an OS\n" "release.\n" "\n" "In IGEL OS 11 the VDI client version is tied to the OS release." ), }, { "heading": "

What to watch

",
"body": ( "An estate with no route to the internet does not reach the portal. IGEL's answer is the\n" "distributed app repository, where devices pull packages from a local server instead, and\n" "that is an Enterprise-licence feature. There is also peer update, where a device pulls from\n" "another device on the same network, and that one is in every edition.\n" "\n" "Which of the two you need depends on how the network is separated." ), }, ], }, "status": { "corpus": 315, "experts": [ { "ref": "experts/michael-steg", "score": "0.40", }, { "ref": "experts/valentina-cicmak", "score": "0.38", }, ], "neighbours": [ { "ref": "solutions/igel", "relation": "parent", }, { "ref": "solutions/microsoft/easylife-365-collaboration", "score": "0.70", }, { "ref": "solutions/omnissa/omnissa-freestyle-orchestrator", "score": "0.70", }, { "ref": "solutions/igel/igel-onboarding-service", "score": "0.70", }, ], "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/igel-app-portal' locale = 'en' labels = [ordered]@{ vendor = 'IGEL App Portal' 'capability/modern-workplace' = 1.69 'capability/automation' = 1.81 'vendor/igel' = 3.03 } annotations = [ordered]@{ source = 'src/content/solutions/en/igel/igel-app-portal.md' route = '/en/solutions/igel/igel-app-portal/' schema = '/nerd/schema/solutions.json' markdown = '/en/solutions/igel/igel-app-portal.md' } } spec = [ordered]@{ title = 'App Portal' tags = @('modern-workplace', 'automation') vendors = @('igel') summary = 'IGEL OS 12 ships with no applications. Everything a person uses arrives from here as a package, and updates without touching the operating system.' 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 = 'product' addon = $false sourceNote = 'soultec.ch/solutions/igel, read 2026-08-30; igel.com product navigation, same day' vendorName = 'IGEL App Portal' status = 'current' sections = @( [ordered]@{ heading = '

What it is

'
body = @'The App Portal is where the applications come from. IGEL OS 12's base image deliberatelycontains none, so the Citrix client, the Omnissa Horizon client, the Azure Virtual Desktopclient and the browsers are all selected in the portal and pushed to devices or devicegroups from there.It is part of the IGEL cloud services.'@ } [ordered]@{ heading = '

Applications as containers

'
body = @'Applications are delivered as containers, managed apart from the operating system. So aclient update is a package of its own and no longer has to be scheduled against an OSrelease.In IGEL OS 11 the VDI client version is tied to the OS release.'@ } [ordered]@{ heading = '

What to watch

'
body = @'An estate with no route to the internet does not reach the portal. IGEL's answer is thedistributed app repository, where devices pull packages from a local server instead, andthat is an Enterprise-licence feature. There is also peer update, where a device pulls fromanother device on the same network, and that one is in every edition.Which of the two you need depends on how the network is separated.'@ } ) } status = [ordered]@{ corpus = 315 experts = @( [ordered]@{ ref = 'experts/michael-steg' score = '0.40' } [ordered]@{ ref = 'experts/valentina-cicmak' score = '0.38' } ) neighbours = @( [ordered]@{ ref = 'solutions/igel' relation = 'parent' } [ordered]@{ ref = 'solutions/microsoft/easylife-365-collaboration' score = '0.70' } [ordered]@{ ref = 'solutions/omnissa/omnissa-freestyle-orchestrator' score = '0.70' } [ordered]@{ ref = 'solutions/igel/igel-onboarding-service' score = '0.70' } ) 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/igel-app-portal", "locale": "en", "labels": map[string]any{ "vendor": "IGEL App Portal", "capability/modern-workplace": 1.69, "capability/automation": 1.81, "vendor/igel": 3.03, }, "annotations": map[string]any{ "source": "src/content/solutions/en/igel/igel-app-portal.md", "route": "/en/solutions/igel/igel-app-portal/", "schema": "/nerd/schema/solutions.json", "markdown": "/en/solutions/igel/igel-app-portal.md", }, }, "spec": map[string]any{ "title": "App Portal", "tags": []any{"modern-workplace", "automation"}, "vendors": []any{"igel"}, "summary": "IGEL OS 12 ships with no applications. Everything a person uses arrives from here as a package, and updates without touching the operating system.", "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": "product", "addon": false, "sourceNote": "soultec.ch/solutions/igel, read 2026-08-30; igel.com product navigation, same day", "vendorName": "IGEL App Portal", "status": "current", "sections": []any{ map[string]any{ "heading": "

What it is

",
"body": "The App Portal is where the applications come from. IGEL OS 12's base image deliberately\n" + "contains none, so the Citrix client, the Omnissa Horizon client, the Azure Virtual Desktop\n" + "client and the browsers are all selected in the portal and pushed to devices or device\n" + "groups from there.\n" + "\n" + "It is part of the IGEL cloud services.", }, map[string]any{ "heading": "

Applications as containers

",
"body": "Applications are delivered as containers, managed apart from the operating system. So a\n" + "client update is a package of its own and no longer has to be scheduled against an OS\n" + "release.\n" + "\n" + "In IGEL OS 11 the VDI client version is tied to the OS release.", }, map[string]any{ "heading": "

What to watch

",
"body": "An estate with no route to the internet does not reach the portal. IGEL's answer is the\n" + "distributed app repository, where devices pull packages from a local server instead, and\n" + "that is an Enterprise-licence feature. There is also peer update, where a device pulls from\n" + "another device on the same network, and that one is in every edition.\n" + "\n" + "Which of the two you need depends on how the network is separated.", }, }, }, "status": map[string]any{ "corpus": 315, "experts": []any{ map[string]any{ "ref": "experts/michael-steg", "score": "0.40", }, map[string]any{ "ref": "experts/valentina-cicmak", "score": "0.38", }, }, "neighbours": []any{ map[string]any{ "ref": "solutions/igel", "relation": "parent", }, map[string]any{ "ref": "solutions/microsoft/easylife-365-collaboration", "score": "0.70", }, map[string]any{ "ref": "solutions/omnissa/omnissa-freestyle-orchestrator", "score": "0.70", }, map[string]any{ "ref": "solutions/igel/igel-onboarding-service", "score": "0.70", }, }, "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/igel-app-portal", locale: "en", labels: { vendor: "IGEL App Portal", "capability/modern-workplace": 1.69, "capability/automation": 1.81, "vendor/igel": 3.03, }, annotations: { source: "src/content/solutions/en/igel/igel-app-portal.md", route: "/en/solutions/igel/igel-app-portal/", schema: "/nerd/schema/solutions.json", markdown: "/en/solutions/igel/igel-app-portal.md", }, }, spec: { title: "App Portal", tags: ["modern-workplace", "automation"], vendors: ["igel"], summary: "IGEL OS 12 ships with no applications. Everything a person uses arrives from here as a package, and updates without touching the operating system.", 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: "product", addon: false, sourceNote: "soultec.ch/solutions/igel, read 2026-08-30; igel.com product navigation, same day", vendorName: "IGEL App Portal", status: "current", sections: [ { heading: "

What it is

",
body: "The App Portal is where the applications come from. IGEL OS 12's base image deliberately\n" + "contains none, so the Citrix client, the Omnissa Horizon client, the Azure Virtual Desktop\n" + "client and the browsers are all selected in the portal and pushed to devices or device\n" + "groups from there.\n" + "\n" + "It is part of the IGEL cloud services.", }, { heading: "

Applications as containers

",
body: "Applications are delivered as containers, managed apart from the operating system. So a\n" + "client update is a package of its own and no longer has to be scheduled against an OS\n" + "release.\n" + "\n" + "In IGEL OS 11 the VDI client version is tied to the OS release.", }, { heading: "

What to watch

",
body: "An estate with no route to the internet does not reach the portal. IGEL's answer is the\n" + "distributed app repository, where devices pull packages from a local server instead, and\n" + "that is an Enterprise-licence feature. There is also peer update, where a device pulls from\n" + "another device on the same network, and that one is in every edition.\n" + "\n" + "Which of the two you need depends on how the network is separated.", }, ], }, status: { corpus: 315, experts: [ { ref: "experts/michael-steg", score: "0.40", }, { ref: "experts/valentina-cicmak", score: "0.38", }, ], neighbours: [ { ref: "solutions/igel", relation: "parent", }, { ref: "solutions/microsoft/easylife-365-collaboration", score: "0.70", }, { ref: "solutions/omnissa/omnissa-freestyle-orchestrator", score: "0.70", }, { ref: "solutions/igel/igel-onboarding-service", score: "0.70", }, ], search: "/en/search.json", },};console.log(JSON.stringify(page, null, 2));

# 67 lines · YAML · validated at build# 85 lines · JSON · validated at build# 92 lines · TOML · validated at build# 105 lines · XML · validated at build# 106 lines · Python · read back at build, equals the JSON record# 103 lines · PowerShell · read back at build, equals the JSON record# 112 lines · Go · read back at build, equals the JSON record# 97 lines · JavaScript · read back at build, equals the JSON record · served at /en/solutions/igel/igel-app-portal.md

Solution · IGEL

App Portal

The vendor calls it: IGEL App Portal

IGEL OS 12 ships with no applications. Everything a person uses arrives from here as a package, and updates without touching the operating system.

Vendors IGEL 3.03
02Capabilities
315Corpus

What it is

The App Portal is where the applications come from. IGEL OS 12’s base image deliberately contains none, so the Citrix client, the Omnissa Horizon client, the Azure Virtual Desktop client and the browsers are all selected in the portal and pushed to devices or device groups from there.

It is part of the IGEL cloud services.

Applications as containers

Applications are delivered as containers, managed apart from the operating system. So a client update is a package of its own and no longer has to be scheduled against an OS release.

In IGEL OS 11 the VDI client version is tied to the OS release.

What to watch

An estate with no route to the internet does not reach the portal. IGEL’s answer is the distributed app repository, where devices pull packages from a local server instead, and that is an Enterprise-licence feature. There is also peer update, where a device pulls from another device on the same network, and that one is in every edition.

Which of the two you need depends on how the network is separated.

Who works with it

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