Getting Started: Combining All Four SPRAPP Products in One Stack

One Stack, Four Roles

SPRAPP's products are designed to work alone or together. This getting-started guide sketches a stack that uses all four — Sprappy Filter, SPRAPP Panel, TinyLM, and smoltext — each doing the one job it's best at. You won't always need all four, but seeing them combined clarifies what each contributes.

Sprappy Filter at the Front Door

Every incoming request hits Sprappy Filter first. It scores for threats cheaply and rejects obvious prompt injection or abuse before any expensive work happens. Putting the cheap screen first protects everything downstream. Setup is in the docs at https://doc.sprapp.com.

TinyLM for Routine, Private, or Offline Work

Requests that the application can handle locally — classification, extraction, short responses, anything privacy-sensitive or needing offline operation — go to TinyLM on-device. This keeps data local and avoids cloud cost for the routine majority. The honest limit is capability: hard reasoning isn't TinyLM's job.

SPRAPP Panel for the Hard, High-Stakes Questions

When a query is genuinely hard, ambiguous, or high-stakes, the stack escalates to SPRAPP Panel, which runs several models and surfaces their agreement or disagreement. Because Filter already screened the input, Panel's expensive multi-model call isn't wasted on junk. This is where you spend the most, so reserve it for questions that justify it.

smoltext at the Boundaries

Wherever small structured payloads cross network or storage boundaries between these components — logs, request envelopes, queued messages — smoltext shrinks them. It's the plumbing optimization, applied only where byte volume actually costs you.

How a Request Flows

A request enters, gets scored by Sprappy Filter, and is rejected if dangerous. If clean, TinyLM handles it locally when it can. If the task exceeds local capability and policy allows, it escalates to SPRAPP Panel. Throughout, smoltext compresses the small payloads moving between services. Each tool runs only when it's the right one.

You Don't Need All Four

Be honest about your needs. Many teams use just one or two of these. The point of seeing them combined is to understand the roles, then take what fits. Adding a product you don't need is cost without benefit.

Next Steps

Each product has its own quick start and reference at https://doc.sprapp.com. Start with the one that addresses your sharpest pain, prove it on real traffic, and add others only as concrete needs appear.