eeCLOUD DaaS Documentation

What You Buy

eeCLOUD is a managed data engine for structured and semi-structured workloads. The commercial unit is the Application: every Application has its own API Key, storage scope, configuration and plan.

• Free plan for onboarding, prototypes and low-volume workloads
• Paid subscriptions for higher scale, more Memories and production operations
• Dashboard for creation, inspection and usage monitoring
• Live OpenAPI and official SDKs for application integration

Getting Started

1. Create an Application in the Dashboard.
2. Copy the API Key associated with that Application.
3. Choose a Memory name for your dataset.
4. Validate the model through OpenAPI or integrate through eeCLOUD.SDK.

using eeCLOUD.SDK;

using var ee = new eeCloudClient("YOUR_API_KEY");

var result = await ee.Memory("orders").WriteAsync(
    new { total = 99.90m, status = "created" },
    reference: 1001
);

Choose the Right Surface

The public OpenAPI reference is available at api.eecloud.io. The official C# SDK is documented in the platform docs and distributed through NuGet.

Core Concepts

Application

The top-level isolation unit of the platform. An Application maps to one eeCLOUD service space, one API Key scope and one subscription plan.

Memory

A logical container for records. Depending on your use case, a Memory can behave like a table, collection, timeline or event stream.

MemoryArea

The stored record returned by reads and writes. A MemoryArea contains JSON payload data plus engine metadata.

Record Semantics

How the SDK Maps to the Service

The official C# SDK is a 1:1 mapping of the public REST API. The most important entry points are:

• new eeCloudClient(apiKey) to connect to your Application
• ee.Memory("name") to target a specific Memory
• WriteAsync, ReadAsync, ReadAllAsync and ReadByReferenceAsync for data access
• UpdateAsync, UpdateValueAsync, DeleteAsync, RestoreAsync and EraseAsync for lifecycle management

For raw route inspection and request/response verification, use the live OpenAPI reference. For day-to-day .NET integration, prefer the official SDK.

Read Model

eeCLOUD reads are order-aware. When multiple records match, the Order parameter decides whether you want the most recent record (DESC) or the oldest one (ASC).

var latest = await ee.Memory("sessions").ReadAsync();
var first = await ee.Memory("sessions").ReadAsync(Order.ASC);

Write and Ownership Model

Writes accept payload data and can also carry ownership and routing metadata such as reference, id, index, date and clusterized.

await ee.Memory("telemetry").WriteAsync(
    id: "sensor-01",
    data: new { temperature = 23.8, battery = 91 },
    reference: 1001,
    clusterized: true,
    date: DateTime.UtcNow
);

Return Model

Memory

MemoryArea

Object Graph Responses

Object graph routes return a wrapper with both eeCLOUD metadata and the resolved object payload. In the SDK this is exposed through ObjectMemory and ObjectMemories.

Backend Notes

eeCLOUD 4.1 supports SQL backends, eeCACHE and the new SFTP backend. Object graph persistence is intended for SQL and eeCACHE-backed workloads. SFTP is available for file-oriented backend scenarios, but not for object graph persistence.

Next