One shell for every area
Capabilities · Platform · Fabric
Lifecycle capabilities, platform control-plane areas and shared fabric — mission-first guides for people using Spanline. Available opens a guide; Coming soon is on the roadmap.
Build
Observe traffic, compose calls, curate data, wire reactions.
Capture
Give every workspace disposable, shareable HTTP inboxes that record exactly what a provider sent — headers, body, signature validity, timing — and make that record reusable by every other capability.
Available
API Studio
Be the request workbench a developer keeps open all day — every protocol the team actually uses, backed by workspace environments and secrets instead of a local file nobody else can read.
Coming soon
Payloads
Stop structured data from living in Slack messages and gists. Store JSON · YAML · XML · CSV once, version it, view it, visualise it, diff it, convert it, and let every other capability consume it by reference.
Coming soon
Automation
Turn the event backbone into a product surface: a visual graph that reacts to Spanline events, calls actions across capabilities, waits for humans when it must, and keeps a per-step record of what it did.
Coming soon
Verify
Prove correctness, then prove it holds under load.
Testing
Own functional truth: API suites first, then UI results ingested from the customer CI. Every failure carries the request, the response, the assertion and the artefact that proves it.
Coming soon
Performance
The deepest capability in the product: k6 scenarios with versioned scripts, thresholds as policy, collection runs as an evidence grid, comparisons against a blessed baseline, and infrastructure snapshots that explain why a number moved.
Available
Ship
Track what is broken, sync with the tools people already live in, gate the version.
Issues
Close the loop from evidence to fix. Small on purpose: one issue, its evidence links, a board, labels, relations. Everything about external trackers belongs to Connections.
Coming soon
Connections
One bridge, many products. An organization installs a provider once; each workspace maps it to the Spanline products it needs, with an explicit direction, conflict policy and import scope — and a conflict queue instead of silent overwrites.
Coming soon
Releases
Make the ship decision explicit and reviewable: a version belonging to a project, a set of gates fed by Testing, Performance and Issues, and a record of every pass, fail and waiver.
Coming soon
Operate
Push events out, watch the whole picture, ask questions of it.
Subscriptions
One reliable outbound pipeline: signed payloads, exponential retries, per-attempt receipts, replay, and a circuit breaker. Slack, Lark and Telegram are destination flavours on that pipeline, not separate products.
Coming soon
Observability
Aggregate every other capability into dashboards, metrics, alerts and generated insights — the reason a manager opens Spanline instead of five tabs.
Coming soon
AI Assistant
Read the evidence graph and answer in context: why did p95 move, which cases went flaky, draft the payload, summarise the release. Every action runs as the asking user, through the same API, with the same audit.
Coming soon
Platform areas
Control plane: identity, tenancy, commerce, governance, operations and growth.
Identity & access
Authenticate a person once at the platform, then apply organization policy before any workspace work begins. Bind machines (CLI devices, org API keys) so a stolen token is not enough.
Available
Organizations
Be the security and policy boundary of Spanline. Exactly one owner. Writes require org admin membership. Platform may peek read-only; never bypass.
Available
Licensing & billing
Decide what a tenant may use and what they owe — without encoding feature checks inside every handler by hand forever.
Coming soon
Audit & governance
One immutable trail across platform, organization and workspace scopes — queryable, exportable, and correlated with request ids in logs.
Coming soon
Security posture
Keep the Spanline security model, checklist and backlog inside the blueprint so upgrade plans never depend on a parallel architecture security doc.
Coming soon
Platform operations
Give Spanline operators a control plane for the deployment itself — health, jobs, flags, mail, backups, regions — without touching tenant business data.
Coming soon
Marketplace & support
Extend Spanline with installable integrations and give paying tenants a plan-aware support channel inside the product.
Coming soon
Shared fabric
Workspace primitives every capability would otherwise reinvent.
Workspace core
Provide the business container for all capability data: membership gate, settings, pins and recents — without becoming a second login boundary.
Available
Environments · variables · secrets · tags
One configuration fabric for every capability: named environments, variables, sealed secrets and tags. Stop every product inventing its own env table.
Coming soon
Projects
Give each product/service under development a durable identity that links Capture, Testing, Performance, Issues, Releases and Connections — without nesting those products under Project in the rail.
Coming soon
Executions · runners · scheduler
One run ledger, one queue and one calendar so Performance, Testing, Automation and API Studio share history, concurrency and schedules.
Coming soon
Event backbone
Declare one event vocabulary and deliver it reliably through a transactional outbox so Automation, Subscriptions, Observability and the Assistant never invent parallel buses. Keep the HTTP hot path to: mutate user state + append outbox + return.
Coming soon
Collaboration
Comments, activity, notifications, saved views and signed share links — built once and embedded everywhere evidence is discussed.
Coming soon
Blob storage
Content-addressed blobs with reference counting and pluggable targets (local disk, Org S3, Platform S3) so Capture bodies, Performance artifacts and Testing evidence share one lifecycle.
Coming soon
Before you start
Three things that save time before you open a guide.
-
Sign in
Open app.spanline.dev and pick the right workspace.
-
Protect catch URLs
Capture shares an Inbox URL with partners — treat it like a secret.
-
Run load outside the browser
Performance uses k6 via the Spanline CLI or CI — not the web app alone.