Skip to content
SolidwayLLM gateway
English中文

Architecture

Transparent by design

The request path has three stages, and only the middle one is ours.

  1. client

    Client

    Your application, any SDK

  2. gateway

    rust

    Solidway

    Routing, accounting, health

    • select target
    • record usage
    • judge health
    • preserve bytes

    • primary

      upstream 5xx

      provider-a/gpt-6-astra

    • fallback

      returns response

      provider-b/gpt-6-astra

A request that fails on the primary target is served by the next target in the chain.

  • 01

    No schema translation

    The gateway does not convert one provider dialect into another. What your SDK sends is what the provider receives, which means new model parameters work the day they ship, without waiting for a gateway release.

  • 02

    Streaming stays streaming

    Server-sent event frames are forwarded as they arrive. Chunk boundaries are preserved, so client-side parsing and incremental rendering behave the same with and without the gateway in the path.

  • 03

    Routing decisions are explicit

    Which target served a request, why a fallback was taken and how long each attempt took are all recorded in the routing trail attached to that request.

Rust

Written in Rust

One statically linked binary. No garbage collector, no interpreter, and no runtime package to install on the host.

  • No garbage collector

    Memory is released at deterministic points, so the tail of the latency distribution is not affected by collection pauses.

  • One file to ship

    The build produces a single binary for x86-64 or arm64. There is no runtime package, no sidecar and no version matrix to maintain.

  • Flat memory under load

    Throughput scales with available cores. Steady-state memory is bounded by the configured connection pools rather than by a heap.

  • Memory safety at compile time

    In safe Rust, the borrow checker rejects the class of defects that produce buffer overflows and use-after-free before the binary is built.

Next step

Talk to us about your architecture

Tell us how your traffic is shaped today. We will walk through where a forward path fits, what the failure policy should look like, and how the gateway would be deployed in your environment.

Request a conversationRead the architecture notes

No pricing on this page. Every deployment is scoped individually.

  • A review of your current provider and key layout
  • A failure policy matched to your error classes
  • A deployment shape for your network