Skip to content
StaryaAI
PortuguêsEnglish

Applied AI · NebulaOS

The technology platform for connecting AI to operations.

NebulaOS connects models, sources and tools and helps monitor the points included in the deployment.

Adoption and context

A defined process. A foundation for growth.

Start with a defined process. The team works in NebulaWorks, supported by NebulaOS and Starya engineering. Expand the scope as outcomes and integrations are verified.

Model, agent, context and gateway: understand the terms
Model
The AI component that generates a response from the information it receives.
Agent
The application that uses AI and tools to perform a task.
Context
The information and instructions available for that task, such as a request, a source or a company rule.
Model gateway
The common access point for models. It helps organize the calls that pass through it and track their consumption.

From request to outcome

A model call is not the entire action.

An agent can talk to a model and then call a system. Observing the first call does not prove the authorization, execution or result of the second.

Fictional example · explore coverage

Choose the integrated path and see which records each part can provide. No system is accessed.

Choose operation
Operation coverage
  1. 01Request
  2. 02Model
  3. 03Authority
  4. 04Attempt
  5. 05Confirmation

Step 1 of 5

Prepare a quote for the received request.

Sales agent receives the request. The request must accompany the following steps.

What can be stated at this stage
Request received. No action attempted.

Reading the integrated path

Model call

Prepare a response

Usage and call recorded in this example

Action control

Human approval required

Rule and owner before the attempt

CRM

Destination system

Verify the action beyond the agent’s response

Read the five steps and their limits
  1. Receive the request and authorized context.
  2. Query the model. The call does not authorize external actions.
  3. Apply a rule or review at the integrated point. Without authority, stop this path; requesting an adjustment returns the proposal.
  4. Attempt the authorized action and record the response.
  5. Check the destination. A missing response means an unknown result, not a proven failure.

If the tool acts outside this path, these controls do not prove blocking, execution or results. Coverage depends on the integration.

The platform connected to what needs to happen

Model access

Organize how people and applications access models and monitor usage and consumption.

Connected context

Bring relevant company information to tasks, considering sources, access and freshness.

Agents and operations

Connect workflows, tools and handoffs to teams and systems.

Monitoring

Connect records, failures, consumption and results to guide operations and their improvement.

Protection with a defined scope

Control needs to reach the point of action.

The gateway is the common access point for models. It tracks calls that pass through that path. Controlling a record update or a submission also requires integrating the point that executes the action.

The design identifies which points need integration to observe, limit and confirm actions. New controls depend on that coverage and the agreed evolution.

Map your operation’s coverage ↗

Controls in real work

From document analysis to the team’s decision.

See how documents, rules, people and systems participate in a claim denial or reimbursement.

Healthcare reimbursement ↗Documents, outstanding information and request review.Corporate expenses ↗Receipt, internal policy and the person responsible for approval.Claim denial analysis ↗Billing and disputes, with evidence from both sides.Medical staffing and schedules ↗Demand, capacity and alternatives for the team.Inventory replenishment ↗Need, proposal, approval and confirmation.

Fictional reference scenarios. They do not represent ready-made packages or customer results.

NebulaOS connects. NebulaWorks brings the work together.

A shared process · fictional example

A request needs to be checked.

NebulaWorks

The team finds the work.

It sees the request, why it is pending, the context needed and the next decision.

Explore NebulaWorks ↗

NebulaOS

The platform connects the operation.

Models, sources, tools, access and usage connect at the points included in the deployment.

Explore NebulaOS ↗

Starya / FDE

Engineering follows the change.

It investigates with the team why the request stopped, adjusts the flow and checks the effect on the process.

Explore Starya / FDE ↗

Daily work, the technology platform and engineering have complementary roles. Features, integrations and responsibilities depend on scope.

Adoption and context

Access can start simply.

A workspace can help teams converse, work with files and complete tasks. This experience is part of the operation’s evolution, connected to the context and systems it needs.

  1. 01Use in daily work
  2. 02Connect context
  3. 03Monitor the operation
Explore the workspace ↗

Infrastructure

Runtime environment and integrations.

Shared SaaS or Dedicated: two deployment options. Dedicated can use OCI, AWS or on-premises infrastructure, subject to technical assessment and the agreed scope.

Deployment and data

Where will this operation run?

Compare SaaS, using a managed environment, with assisted deployment in your infrastructure. Also explore coordination between environments.

Compare options ↗

For the technical team

Connect your systems through APIs.

APIs are interfaces for integrating systems. The reference details agents, conversations and events.

Consult the API reference ↗