Nexus BYOC is available only on Enterprise plans.
Fireworks AI features
- Serverless inference: Call models on shared capacity and pay per token.
- Dedicated deployments: Reserve capacity for a model when you need predictable throughput.
- Fine-tuning: Tune a model on your own data and serve the tuned model from the same platform.
Nexus integration
Nexus uses models at several points, which Nexus model guidance describes. In BYOC, the inference proxy routes every model call according to your model catalog,inference-proxy-models.toml. Each catalog entry names an upstream model, the endpoint that serves it, and the secret that holds its API key. Fireworks exposes an OpenAI-compatible endpoint, so a Fireworks model is a catalog entry with api_style = "openai" pointed at that endpoint.
Once Fireworks models are in the catalog, they behave like any other model:
- Work-area defaults: The catalogโs
phase_defaultsassigns a default model to each work area (Query, Curation, and System). A call that names no model runs on its work areaโs default. - Per-query selection: A query can name any enabled model by its catalog ID, and the model selector on a contextโs Query tab lists every model enabled for Query.
- Embeddings: You can optionally route the default embedding model to Fireworks. The setup guide keeps reranking on a Pinecone-hosted model.
Benefits
- Lower curation cost: Curation runs a model across every source, which makes it the most cost-sensitive step in Nexus. A fast open model as the Curation default keeps that cost down as your corpus grows.
- Open models for every work area: You can run Query, Curation, and System on open models, and compare them against closed models on your own questions.
- Fine-tuned models: You can fine-tune a model on Fireworks and serve it to Nexus by adding it to your catalog.
Key concepts
To set up Fireworks models, see Use Fireworks AI models in Nexus BYOC. For supported models and catalog fields, see the Fireworks AI reference.