SaaS
Operated for you
Skytale is delivered as a service operated for your organisation.
What we discuss
Service requirements, configuration and responsibilities shared between you and the provider.
Product
One platform for chat, voice, video and file sharing
Skytale is available as apps for iOS and Android, desktop apps for Windows and Mac, and an administration portal where your organisation manages users, groups and access. Available as SaaS or on-prem.
- iOS
- Android
- Windows
- Mac
For those who already have access. Download Skytale
Settings
Application settings
Each user can customise the app in Settings. Choose light or dark mode, change language and display messages compactly or as bubbles. About shows the app version you are running.
- Contact list.
- Theme and profile settings.
- Tips and tricks, customer support and release notes.
- Biometric authentication and more.
Products
Six parts, one platform
Admin
Skytale Admin
The administration portal where your organisation's administrators manage user access, security groups and settings. It comes with best-practice defaults and gives your organisation full control over its own configuration and data.
Desktop
Skytale Desktop
Skytale on your computer, for Windows and Mac. Find downloads and installation help on the download page.
Web
Skytale Web
Browser version for Chrome, Safari and Edge.
API
Skytale Partner API
A service for external partner applications. It handles communication between designated users and devices and provides access to integrated services. Planned for 2026.
Language
Nine languages in the app
- Norsk
- Nynorsk
- Svensk
- Dansk
- Engelsk
- Tysk
- Fransk
- Spansk
- Ukrainsk
- Finsk
Coming soon - Portugisisk
Coming soon - More languages
More languages can be added on request.
Features
What the platform does
| Chat and group chat | Internal and external communication in chats defined by the user, based on the organisation's contact list. |
|---|---|
| Channels | Internal and external communication in channels created and closed by the organisation. |
| Voice and video | One-to-one and group calls with the same access controls as chat. |
| Video conferencing | Meetings for small and large groups, with screen and file sharing. |
| File sharing | Share and read files and multimedia, up to 100 GB per file. |
| Location sharing and maps | Share locations in chats and channels. |
| Administration and user management | Security settings for individuals, groups and the organisation. |
| End-to-end encryption | Content is encrypted from sender to recipient. |
| TLP marking | The sender selects a sensitivity label under the Traffic Light Protocol, and the label stays with the message. |
| Closing channels | Channels can be closed when the matter is concluded, so access does not remain open. |
| Archive | Older conversations can be archived for later use. |
| Multi-factor authentication | Sign in using two-factor authentication, PIN and Face ID, and/or your organisation's own IAM service. |
| No self-registration | Users are created by the organisation, not by individuals. The organisation verifies its own users. |
On the roadmap
These features are in development and are not included in today's service.
- Threads and replies to individual messages.
- New map features.
- More simultaneous voice and video participants, increasing from 6 to 12, with an SFU (Selective Forwarding Unit).
- Push-to-talk (PTT): encrypted live voice to individuals or groups, like a walkie-talkie.
- @Name mentions in chats and channels.
- Contact cards with shortcuts.
- File Vault: your own encrypted storage space for your files.
Message marking
Who may the message be shared with?
Skytale supports the Traffic Light Protocol. The sender chooses a label when sending a message. The organisation enables or disables TLP in the administration portal. With mandatory TLP, the user must select a level before sending. If TLP is disabled, no label is applied. Choose a level below to see what it means for the recipient.
TLP:CLEAR
May be shared publicly
No restrictions on further sharing. Information may be shared freely and publicly, provided copyright and licences are respected.
Use and risk. Used when information carries little or no foreseeable risk of misuse. Replaces the TLP:WHITE label from the previous version of TLP.
Who may receive it
- Anyone, including outside your community
TLP:GREEN
Within the relevant community
May be shared with colleagues and partner organisations within the relevant community, such as the cybersecurity community, but must not be published or shared through public channels.
Use and risk. Used when information can improve situational awareness in a wider community, for example when warning of threats.
Who may receive it
- Recipients
- The relevant community
TLP:AMBER
With those who need the information
May be shared within the recipient's organisation and with its clients, but only with those who need to know.
Use and risk. Used when recipients need support to act on information, but sharing beyond the organisations involved creates risks to privacy, reputation or operations. Clients are those receiving cybersecurity services from the organisation.
Who may receive it
- Recipients
- Your organisation, on a need-to-know basis
- Clients, on a need-to-know basis
TLP:AMBER+STRICT
Only within your organisation
May only be shared within your own organisation with those who need to know. Sharing with clients, partners or other external parties is not permitted.
Use and risk. Introduced in TLP 2.0 to distinguish clearly between internal sharing and sharing with clients.
Who may receive it
- Recipients
- Your organisation, on a need-to-know basis
TLP:RED
Individual recipients only
For individual recipients only. Information must not be shared beyond those directly participating in the meeting or conversation.
Use and risk. Used when information cannot be handled without significant risk to the privacy, reputation or operations of those involved.
Who may receive it
- The original recipients
TLP specifies sharing rules, not a security classification or a technical restriction on forwarding. The sender may impose additional restrictions. Read TLP 2.0 at FIRST
Getting started
From first conversation to everyday use
Step 1 of 4
Who will use the channel?
We discuss who will use the channel and the requirements that apply to your organisation.
Step 2 of 4
Configured for your organisation
The administration portal is configured with best-practice defaults.
Step 3 of 4
You control who takes part
Your organisation creates its own users within the scope you choose.
Step 4 of 4
A familiar channel before you need it
The channel is put to use in a real case or exercise, before a crisis occurs.
Step 1 of 4
Deployment
Choose the deployment model that fits your organisation
Skytale is available as SaaS or on your own infrastructure. The choice depends on your organisation's requirements and how much control it needs over operations.
Norwegian data storage and jurisdiction
No data is stored outside Norway. Data is processed under Norwegian law.
We clarify operational responsibility, support and prerequisites together before you choose a solution.
Find the right deployment modelNext step
See the platform in use
We demonstrate the administration portal, the app, and how to set up and close a room.