---
title: "IceBox"
url: https://docs.zeroc.com/ice/3.8/services/icebox
docs_index: https://docs.zeroc.com/llms.txt
---

> For an index of every page, see [llms.txt](https://docs.zeroc.com/llms.txt).

# IceBox

An IceBox server hosts IceBox services. You implement each service as a dynamically loadable component, and the IceBox server loads the services that its properties list. You can also administer an IceBox server remotely. You write IceBox services in C++, C# or Java.

This architecture offers several advantages:

- You compose an application from services by configuration, not by compiling and linking. Because a service does not depend on the server that hosts it, you can combine services in one IceBox server or separate them as needed.
- Several services share one process, and in Java and C# one Java Virtual Machine or .NET runtime, which conserves operating system resources compared with running each service as a separate server.
- Services that use a [shared communicator](https://docs.zeroc.com/ice/3.8/services/icebox/configuring-icebox-services.md#using-a-shared-communicator) take advantage of Ice's [collocation optimizations](https://docs.zeroc.com/ice/3.8/runtime/collocated-invocation-and-dispatch.md): an invocation from one of these services to another is a collocated invocation.
- IceBox support is [integrated into IceGrid](https://docs.zeroc.com/ice/3.8/services/icegrid/icebox-integration-with-icegrid.md), the server activation and deployment service.
