Live demo
Try swServer in your browser.
The swServer workspace running live, with files and apps behind one login. Launch it, then follow the steps below.
You'll be assigned one of 10 shared demo accounts. We show you the username and password first — then you open the demo, so you have them in front of you on the login page.
Your demo account — you need these on the login page:
- Username
- Password
Opens in a new tab. Leave this tab open — the password stays here if you need to look again.
See the value in five minutes
Launch the demo above, then try these five steps.
- Sign in once. One login opens the whole workspace. There is no second password for any app.
- Open Files. Your drive is ready, with no “connect a cloud” step.
- Create or edit a document. Create a document in Files and open it. Open it in a second tab to see two people edit at the same time.
- Launch another app. Open the launcher at the right end of the dock: calendar, mail, chat, PDF reader and more, all behind the same login.
- See the administrator side. Sign in as
demo1and open the Admin Panel. Assign apps to groups and end a user’s sessions.
Manual login — pick any account
Want to come back to the same files and chat history later? Pick a specific account here, log in directly, and bookmark it. Just remember it's shared with everyone else who picked the same one.
The ?login_hint= URL parameter is the standard OIDC
way to pre-fill the username field on the Keycloak login form.
You only have to type the password (username + the suffix
demodemo — see the cards above). We never put
passwords in URLs, since URLs leak into browser history, proxy
logs, and screenshots.
About this demo environment
- Shared accounts. The demo runs ten reusable users
named
demo1throughdemo10. Each password is the username with the suffixdemodemo— sodemo1logs in withdemo1demodemo. If two visitors land on the same account at the same time, one will be kicked into a read-only session. Pick a different number from the list below if that happens. - Files reset every six hours. Anything you upload, create, or delete is wiped on a regular cron. Don't store anything important.
- This is not production. The demo runs on a single modest VM. Performance is fine for one or two simultaneous visitors and noticeably slower with a crowd. The architecture you'd actually deploy is the same; only the box is smaller.
- The AI is slowed down for the demo. The built-in
assistant runs a local
Gemma 4model on CPU only — the demo VM has no GPU — so it's slower and less capable here than on a real deployment. It's included to show the feature works, not to represent production quality. A GPU-backed deployment runs a larger, faster model. - One admin account.
demo1is an organisation administrator, so it can see the Admin Console (user management, app catalog).demo2–demo10are regular users. Log in asdemo1if you want to explore the admin side.
Evaluating it for your organisation?
Talk to us about a pilot, deployment or the security review. Nothing is for sale yet; pilots are free of charge.