New environments land in São Paulo.See the product

AI for the people who sell for you

Each partner gets their own agent — memory, tools, and a spend cap. Their data does not mix. You keep the brand.

Built on Google Cloud

southamerica-east1

  • Vertex AIgemini-2.5-flash
  • Cloud Runmin-instances: 0
  • GKEsandbox pool
  • BigQuerytelemetry.events
  • Cloud Storagegs://weights/v3
  • Secret Managerscope: partner
  • Cloud IAMroles/partner.agent
  • Pub/Subaudit.stream
  • Cloud Loggingtenant=atlas-sp
  • Gemmaopen weights

Product

Four parts. One system for the channel.

Agents

An agent per partner, with its own tools and memory. Their customers never see another partner’s context.

  • The models you already meant to use

    Gemini, Gemma, or a compatible endpoint. No rewrite of the partner’s stack.

  • Shaped to the traffic

    Chat, batch, or a spike at month-end. The endpoint follows the load.

  • You keep the face of it

    We run the runtime. The partner sees your product, not ours.

agent.py
from orbysoft import Agent, tool

agent = Agent(
  model="gemini-2.5-flash",
  region="southamerica-east1",
  memory="per_partner",
  monthly_cap=1200,
)

@tool
def crm_lookup(lead_id: str) -> dict:
  return crm.get(lead_id)

@agent.partner_scoped
def qualify(lead):
  return agent.reason(lead, tools=[crm_lookup])
$ orby run qualify --partner atlas-spscopeatlas-sp · isolatedmodelgemini-2.5-flash · 42msresultscore=86 next=book_demo

Training

Fine-tune when you have the data. The job runs, you get a versioned endpoint back.

  • Ordinary training jobs

    SFT or LoRA. You send the dataset. We return a version you can promote.

  • No cluster to babysit

    Jobs go up on Cloud Run or GKE and come down when they finish.

  • One GPU or a few

    Ask for the size the job needs. Don’t pay for a rack you are not using.

Sandboxes

A short-lived machine for an agent that needs to run code or open a file. Snapshot it. Throw it away.

  • Many at once

    Spin up a lot of sandboxes when a rollout needs them. They do not share disks.

  • Your image or ours

    Start from a default image or the one the channel already uses.

  • It shuts itself off

    CPU and memory follow the job. Idle time does not sit on the bill.

Functions

A function becomes an HTTP endpoint. It grows with traffic and goes quiet when nobody calls.

  • Work in parallel

    Fan out a batch without writing your own queue.

  • Long jobs in the back

    Leave a run going. Checkpoint lands in Cloud Storage.

  • A door on the front

    Auth, a cap per partner, and a log you can read later.

Platform

What you need to ship AI to a channel

Where it runs

São Paulo first. Other regions if you need them.

Default region is São Paulo. We can stand up another Google Cloud region if a customer asks.

  • São Paulosouthamerica-east1active
  • Iowaus-central1on request
  • Belgiumeurope-west1on request
  • The primitives

    Functions for short work, sandboxes for untrusted code, agents for the conversation.

  • Files next to the job

    Weights, datasets, and images sit close to where the run happens.

  • Containers that start fast enough

    A runtime for large images and a queue when a job needs an accelerator.

  • Scale with the partners who are actually on

    Idle tenants should not keep machines warm.

  • Training when you need it

    Training jobs can take a GPU or TPU on Vertex AI when you need them.

  • You can see what broke

    Logs and alerts per tenant, so a partner issue stays a partner issue.

In production

The boring parts that keep a channel safe

Access control, logs, and a bill you can show a partner.

orbysoft · consoleLive
atlas-spisolatedcap 82%
Qualify this lead from Recife.
agent · atlas-sp · 42msAtlas scope. Score 86. Mid-tier budget. Next: book a demo.

memory.write · tenant atlas-sp · 42ms

norte-rjisolatedcap 46%
What is the lead time to Niterói?
agent · norte-rj · 38msNorte scope. Delivery in 3 business days with the partner carrier.

memory.write · tenant norte-rj · 38ms

delta-baisolatedcap 71%
The customer asked for a copy of the invoice.
agent · delta-ba · 51msDelta scope. Copy generated and sent to the email on file.

memory.write · tenant delta-ba · 51ms

Ask this partner’s agent…
Live
Audit log, sample events
TimeActionActorIP
10 Sep, 13:54sandbox.createpartner-bot203.0.113.24
10 Sep, 13:41memory.writeatlas-sp198.51.100.7
10 Sep, 13:32deploy.terminatedeploy-bot203.0.113.9
10 Sep, 13:20cap.warndelta-ba198.51.100.31
10 Sep, 13:14image.pushci-runner203.0.113.50
10 Sep, 13:08agent.invokenorte-rj198.51.100.12
10 Sep, 13:02volume.deleteorby-bot203.0.113.77
10 Sep, 12:47secret.readatlas-sp198.51.100.7

8 of 8 events

Spend cap by partner

  • atlas-sp82%
  • delta-ba71%
  • norte-rj46%

delta-ba crossed 70% of its cap. Alert sent at 13:20.

  • One partner, one box

    IAM, audit logs, and data that stays where you put it. Built with LGPD in mind.

  • Logs you can hand over

    What ran, who called it, what it cost. Export if you already have a sink.

  • A cap, then the meter

    Pay for what the code uses. Set a ceiling per partner so a runaway job does not surprise you.

How we run it

How the product is hosted

OrbySoft runs on Google Cloud. São Paulo is the home region. Agents use Gemini through Vertex AI.

Regionsouthamerica-east1

IdentityIAM and Secret Manager

Entry

Partner request

Arrives with the partner’s scope. IAM decides what it can touch.

POST /qualify

Runtime

Cloud Run and GKE

Where functions and sandboxes run. They scale down when the channel is quiet.

instances 0 → 3

Models

Gemini and Gemma

What the agents call today, through Vertex AI. We can point at another model if the job needs it.

gemini-2.5-flash · 42ms

Data

BigQuery and Cloud Storage

Telemetry, evals, and versioned weights. One partner’s data does not train another’s model.

telemetry.events +128/min

How we charge

Subscription plus usage

A platform fee, then tokens and compute. The invoice can split by partner.

  • platform18%
  • atlas-sp34%
  • delta-ba28%
  • norte-rj20%

Start with one partner

Tell us about the network. We’ll stand up an environment with a spend cap.

We reply within one business day.

  1. 01Tell us about the network

    A 30-minute call: how many partners, which channel, what data already exists.

  2. 02An environment with a cap

    We spin up an isolated environment in São Paulo, with a spend cap per partner.

  3. 03First partner live

    One partner starts using it. The rest join when you are ready.