digitalsilo.io

What It Is

Digital Silo is a task-driven Serverless platform for Azure. Its core idea is to package stateless business tasks as Grains and run them in an asynchronous, scalable cloud environment. It aims to abstract away the complexity of infrastructure, queues, execution, and progress callbacks, allowing .NET developers to focus on business logic.

Core Capabilities

The platform consists of storage for Grain DLLs, a Gateway Web API that accepts JSON payloads, Serverless execution infrastructure, and SignalR Service for state callbacks. Developers submit tasks or batches of tasks through a single REST endpoint. Results are not returned synchronously by the API; instead, they are delivered asynchronously via WebSockets/SignalR. It supports task dependency chains, queuing, delayed execution, Durable execution, termination of running tasks, and recovery from the point of interruption after failures.

Tech Stack and Integration

Digital Silo is clearly oriented toward .NET and Microsoft Azure. The documentation requires .NET Core 3.1, the examples use C#, and it references Visual Studio, VS Code, Xunit, FluentValidation, and Microsoft dependency injection. Although the Gateway API is RESTful and, in theory, any language can submit JSON tasks, Grain development mainly depends on the .NET SDK. For deployment, it provides Terraform scripts that can be used in the user’s own Azure subscription, with optional paid hosting by the team.

Pricing

The Development plan is free, but its Docker container is only for developing Grains and cannot be used commercially. Silver costs $299/month or $2,499/year, Gold costs $499/month or $4,199/year, and Enterprise requires contacting the team. Pricing is per instance and excludes taxes; Azure resource costs are billed separately. As a result, the actual cost needs to be evaluated based on task volume, Azure SKU, and runtime model.

Pros, Cons, and Who It’s For

Its strengths are a clearly defined architecture, straightforward REST + SignalR integration, fairly complete code and API examples in the documentation, and the ability to self-deploy on Azure. Its drawbacks are strong dependencies on Azure, Azure AD B2C, SignalR, Terraform, and .NET, making the initial setup relatively demanding. Information about its open-source license, payment methods, SLA, and company background is also limited. It is better suited to teams already running .NET applications on Azure that need asynchronous task orchestration and progress visualization. It is less suitable for scenarios that require cloud neutrality or a multilingual task runtime.

Access from China and Alternatives

The main materials do not provide information about access from mainland China, payment, or compliance. Since it depends on Azure and GitHub, real-world availability needs to be tested, so it is currently rated as unknown. Comparable alternatives include Azure Functions, Durable Functions, Temporal, Hangfire, AWS Lambda, Google Cloud Functions, and similar solutions.