Scoped to your requirements
Managed
We host and run it, and agree the configuration with you.
Agree before you sign off
- Storage and inference region
- Identity and access configuration
- Operations and support owner
- Backup, recovery and incident terms
Deployment
Those three words are only a starting point. What matters is where each kind of data goes, which supplier processes it and who runs each control.
Three ways to deploy
Scoped to your requirements
We host and run it, and agree the configuration with you.
Agree before you sign off
After an architecture review
Marella AI can be deployed into a customer-controlled cloud environment after architecture review.
Agree before you sign off
A package exists; we agree what you need to run it
A self-hosted deployment package is available; prerequisites and responsibilities are agreed during architecture review.
Agree before you sign off
Data-flow review
A proper review follows the copies too: the text pulled out of the files, what gets sent to the model, and the backups and logs.
Original files, connected records, versions, deletion and access changes
Parsed text, page coordinates, chunks, metadata, embeddings and extracted structures
Queries, retrieved context, prompts, model/provider requests and generated outputs
Identity events, decision traces, security events, logs, support access, backups and recovery copies
Who does what
For each one, write down who sets it up, who runs it and who signs it off: sign-in, storage, models, patching, monitoring, backups, incidents, deletion and support.
No universal region is advertised. Data location depends on the selected managed, customer-cloud or self-hosted architecture and is stated during review.
Not by default. Network egress, model access, updates, licensing, telemetry and support routes must be designed and tested for the required environment.
That changes by configuration. The order form and responsibility matrix should name the owner, coverage, access route, recovery expectations and escalation process.
It can be reviewed, but a change in storage, identity, model, network or operator boundary creates new security, performance and support assumptions that require validation.
Keep the first message non-confidential. We agree a secure route for diagrams, questionnaires and sample documents afterwards.