What is Citrix Secure Developer Spaces?
Developer
Citrix Secure Developer Spaces™ (SDS) gives you a powerful, pre-configured development environment you can open in seconds — from any device, any browser, or your favorite IDE. Think of it as your own dedicated Linux dev machine, always ready, always consistent, and accessible from anywhere.
This guide explains what SDS is, how it compares to what you’re used to, and introduces the key concepts you’ll encounter.
How it works
Your workspace is a full Linux development environment running in the cloud. It has everything your project needs — IDE, terminal, source code, build tools, and dependencies — set up and ready to go. You connect to it from your browser or a locally installed IDE.
When you log in to SDS, you’ll see your project and available workspace templates. You pick a template, select launch, and within seconds you have a running environment with your repositories cloned, your tools installed, and your IDE connected. That’s it — you’re coding.
What’s in it for you
Start coding in minutes, not days
No more “install this, configure that, ask Dave for access.” Your workspace comes pre-loaded with everything your project needs — the right language runtimes, build tools, dependencies, and repository access are already configured.
Your tools, your way
Use your dotfiles, extensions, keybindings, and shell configuration. SDS supports VS Code (browser and desktop), JetBrains IDEs, Cursor, Windsurf, Kiro, and any other editor that connects over SSH. You choose how you work.
Any device becomes a dev machine
Work from your laptop, a thin client, a tablet, or even a borrowed machine. Your workspace is the same everywhere because it runs in the cloud, not on your local hardware.
Power when you need it
Need more CPU for a heavy build? GPUs for ML training? Scale resources on demand — no hardware requisition required. Your workspace can be more powerful than any laptop.
Experiment freely
Spin up a new workspace in seconds. Try something risky, break things, throw it away, start fresh. The cost of experimenting is near zero.
Consistent environments across the team
Everyone on your project uses the same base tools, same versions, same configuration. If it works in your workspace, it works in everyone’s. “Works on my machine” stops being a thing.
What stays the same
If you’re coming from a laptop, VDI, or WSL-based workflow, most of what you know still applies:
- Git workflow — Clone, branch, commit, push. Same as always.
- Terminal — Full Linux shell with your tools, aliases, and scripts.
- IDE — Connect your desktop IDE or use the browser-based version. Your choice.
- Your files — Everything you save under your home directory persists between sessions.
- Root access — You have full control inside your workspace.
What’s different
SDS changes where your development happens, not how you develop. Here’s what’s actually different:
| Traditional setup | With SDS |
|---|---|
| Code lives on your laptop | Code lives in your cloud workspace (can’t lose it if your laptop dies) |
| You install and maintain your own tools | Your Project Owner configures the base environment in a template |
| Hardware limits what you can build | Workspace resources scale independently of your device |
| Environment setup takes hours or days | Launch a pre-configured workspace in seconds |
| “Works on my machine” debugging | Everyone shares the same base environment |
| Onboarding a new project = manual setup | Pick a template and start coding |
The key mental shift: Your laptop (or browser) is a window into your workspace, not the workspace itself. Everything runs in the cloud — your device is just the screen.
Key terminology
These are the terms you’ll see when using SDS:
| Term | What it means |
|---|---|
| Workspace | Your personal cloud development environment. It contains your IDE, code, tools, and terminal. You can have multiple workspaces for different projects or branches. |
| Template | A pre-configured workspace blueprint created by your Project Owner. It defines the container image, tools, repositories, and resource allocation so you can start immediately without manual setup. |
| Project | An organizational unit that groups related workspaces, users, and resources together. You’re assigned to one or more projects by your Project Owner. |
| Project Owner | The person who manages your project’s configuration — templates, resources, access controls, and team membership. They’re your first point of contact for project-specific questions. |
| Profile | Your personal settings — work schedule, Git credentials, shell configuration, secrets, and IDE preferences. These apply across all your workspaces. |
| Integrations | Connections to external services (GitHub, GitLab, Bitbucket, Azure DevOps) that let your workspaces access code repositories seamlessly. |
| Workspace Apps | Applications running inside your workspace (like a dev server) that you can access from your browser or share with teammates. |
| Cloud IDE | The browser-based VS Code editor built into SDS. No installation needed — just select it to open. |
How SDS fits into your day
A typical day with SDS looks like this:
- Start your day. Open your browser or IDE. Your workspace may already be running (based on your work schedule) or starts in seconds when you connect.
- Write code. Pull latest changes, work on your feature, run tests — just like you would on a local machine.
- Preview and share. Run your application and access it through Workspace Apps. Share a live preview with teammates without deploying anywhere.
- End your day. Close your browser or IDE. Your workspace pauses automatically based on your schedule, saving resources. Everything is there when you come back.
Frequently asked questions
Is this just VDI for developers? No. VDI streams a desktop image to your device. SDS gives you a real Linux development environment — full terminal access, root permissions, native IDE connectivity, and the ability to run containers and services inside your workspace. It’s built for development workflows, not desktop virtualization.
Do I lose my work when I close my browser?
No. Your home directory (/home/developer) is persistent. Files, code, and configurations are saved between sessions. However, system-level changes outside of /home/developer are reset when a workspace restarts — use startup scripts or ask your Project Owner to update the template for those.
Can I use my own dotfiles and IDE settings?
Yes. SDS supports personal shell configurations (.bashrc, .zshrc), IDE settings, VS Code extensions, and startup scripts. Configure these once in your profile and they apply to every workspace.
Can I work offline? No — SDS workspaces require a network connection since they run in the cloud. If you lose connectivity, your work is saved up to the last change, and you can reconnect and resume where you left off.
What about security restrictions? Your organization may apply specific security policies (like clipboard controls or network restrictions). These are configured by your platform administrator to protect sensitive code and data. If you encounter a restriction you don’t understand, ask your Project Owner or platform administrator.
Next steps
Ready to get started?
- Quick start: Set up your account — Configure your profile, Git access, and credentials.
- Quick start: Create and connect to your workspace — Launch your first workspace and connect your IDE.