Services

Services and
deliverables.

Choose a starting point. Each scope is built around your tasks, users and operating requirements.

02

Agent Setup & Workflows

Claude Code and Codex environments built around your projects: specialist agents, reusable skills and tested procedures, with the context to continue the work.

What you can commissionAgent roles · skill libraries · project context · workflow optimisation

Explore agent setup & workflows →Inspect the workflow example →

Start with a scoped brief and, where useful, one working prototype. The proposal names the deliverables, review points and acceptance checks before the build is extended.

How a project works →
On-site GPU rental with Locus Hardware, setup and responsibilities

Adel Labs × Locus

Private compute.
Without buying a server.

A private model environment without buying the GPUs upfront. Locus provides the leased infrastructure; Adel Labs builds the working system around your research and team.

Adel LabsModel setup & integration

The system your team uses.

We install the selected model, connect approved documents and tools, and test the agreed tasks. Your handover includes the interface, configuration and operating instructions.

From leased hardware to a research environment your team can operate.

Fully local. Offline when required.

Keep model inference, document retrieval and outputs inside your environment. For offline delivery, we test the complete workflow with the external connection disabled.

Capacity and pricing follow an assessment of the model, document length, concurrent users and support needs. Any remotely hosted option is scoped separately.

Compare local, cloud and hybrid →
Prepare a GPU deployment brief

Before we begin

Before your project begins.

Is Adel Labs a fit for my project?

Start with a specific task: a website that explains an offer, a workspace for approved documents, a recurring process or a research tool. We define who will use it, what they need to do and how the result will be checked.

How are the fee and schedule agreed?

The proposal sets the deliverables, fee, schedule and review points before implementation. Content preparation, integrations, data handling and acceptance requirements affect the scope. A prototype can resolve an open question before a larger build is agreed.

Where will our information be processed?

The scope names where documents, processing and outputs sit. Offline, private team and connected workspaces have different boundaries. External providers and connections are agreed explicitly; an offline claim requires a disconnected acceptance test.

Compare operating modes →
What do we own at handover?

The proposal identifies the source files, configuration, documents and access you receive. Third-party model and software licences remain applicable. You receive operating instructions and an agreed backup/export route.

What happens after launch?

A one-time build includes agreed acceptance checks and a walkthrough. Maintenance, update testing, support allowance and further development can be scoped separately.

How does a project begin?

Prepare a brief with the task, the tools you use and the required result. We agree the included work, fee, schedule and review points before implementation. The first engagement can be a scoped prototype when the full build still needs to be defined.

Your next project

Define your
next project.

Start with the task, who will use the result and what needs to improve.