STEWARD by SOLEUM VS https://alanaknows.com/

• Live reads under the user's login
  Reads your REST API at the moment of the question, with the signed-in user's own token. No index and no copy of live records. Your API decides what each user sees. Live reads need an app with signed-in users. Public sites get knowledge-base answers.
• Opaque credential pass-through
  The user's token passes through unread. STEWARD never parses, validates or stores the token, and the model never sees it. No service credential exists to steal.
• Full trace per answer
  Every answer writes a trace: prompt, response, source excerpts with provenance, tool calls and cost. Your team sees the same record our operators see.
• Cited answers
  Inline citations link each claim to its source excerpt, followed by the sources and an audit line. Source, timestamp, input and output. Logged and exportable.
• Grounded answers, engineered refusal
  An adaptive relevance threshold gates every answer. Below the threshold, STEWARD reports no relevant context in your material and names the next step. No improvised answers.
• Cost per answer
  See the cost and stop reason of every answer. Every billed credit links to the trace behind it.
• AWS Bedrock, sole model provider
  AWS Bedrock is the sole model provider, reached through a private endpoint. No LLM API key exists anywhere in the platform.
• Content processed by AWS alone
  AWS services alone process your corpus, prompts, answers, retrieved context, history and telemetry. AWS commits that Bedrock stores no inputs or outputs and model providers never train on them.
• Input and output guardrails
  An input guardrail checks every question before any model call. An output guardrail checks every answer before delivery.
• Personal data redacted at delivery
  Personal data is redacted at delivery, with a hard fail on residue. A response with residue is replaced before the user sees the text.
• Sealed analysis sandbox
  Analysis code runs in an isolated sandbox: import allowlist, 2 GB memory, 30-second hard cap, no network in or out.
• Bounded execution
  Every turn runs under a hard deadline, with the tool loop capped at seven steps. Each turn ends in one of six named states, and degraded states carry their cause.
• Platform-neutral
  Embeds in any web product. Independent of any CRM, help desk or software suite. One engine, any industry.
• Knowledge base connectors
  Connect GitHub and Google Drive, with several sources per product. Webhooks re-sync content when a source changes. STEWARD ingests only the sources you designate.
• Hybrid retrieval
  Vector and keyword search run together and merge by reciprocal rank fusion, weighted 0.7 to 0.3. Exact terms and meaning both count.
• Embeddable widget
  Three modes: classic, flyout and embedded. Configure in the console and paste the snippet where your people work. Nothing to rip out.
• Playground with framework snippets
  A public playground previews the real widget and emits HTML, React or Angular snippets.
• Chat API
  The same streamed answer, citations, guardrails and trace the widget gets, by API. Supports cancel and returns typed events. Build STEWARD into your own surface.
• Control-plane API
  Everything the console does, by API: products, sources, keys, members, traces and billing reads. Provision one expert per client from your own code. Available on Enterprise.
• Scoped keys
  Publishable keys are product-scoped, origin-bound and rate-limited. Secret keys carry a mandatory expiry, are stored as fingerprints and show once. A revoked key stops working in about 12 seconds.
• Per-key origin allowlists
  Add a customer domain with a key edit. No deploy.
• Multiple experts per account
  Run separate product experts in one account, each with its own sources, widget and keys.
• Attributed audit log
  Every console change writes one attributed audit entry, committed with the change and never edited.
• Usage and billing visibility
  Credits shown by category and by product. Allowance and bundle balance appear as separate numbers. Alerts fire at 80% of the allowance by default.
• Billing never touches your data
  No billing event deletes, pauses or freezes your data. End users never see a billing message.
• Operator console
  Home, Traces and Dashboards, Products, Data sources, Billing, Account and the audit log, in one console.
• Separated production
  Production and staging run in separate AWS accounts. Production deploys only by manual dispatch of a commit with green CI.
• Edge protection and monitoring
  A regional WAF with 12 rules. 30 CloudWatch alarms on production, each routed to a confirmed channel.

• Domain still registered
  The domain alanaknows.com is still owned and registered, meaning the owner has the option to reactivate or rebuild the site in the future rather than losing the domain entirely.
• Placeholder prevents dead link errors
  Instead of showing a generic browser error (like a DNS failure), the hosting provider displays a suspended page notice, which can be less confusing to visitors than a broken connection.
• Potential for future content
  Since the domain is intact, if the account issue is resolved, the original website content could potentially be restored without needing to re-register the domain.
• Clear indication of status
  The suspended page URL (cgi-sys/suspendedpage.cgi) clearly signals that this is a hosting-related suspension rather than the site being permanently deleted, which can help users or search engines understand the temporary nature of the outage.
• No malicious content risk
  Because the site is suspended and not actively serving custom content, there is no current risk of the site hosting malware, spam, or other harmful material that active but neglected sites might accumulate.

Possible disadvantages

• Website is completely inaccessible
  The main URL redirects to a suspended page, meaning visitors cannot access any actual content, information, or services that the site was intended to provide.
• Unprofessional appearance
  A suspended page gives a poor impression to visitors, potential clients, or collaborators, suggesting neglect, financial issues, or abandonment of the site or associated business/brand.
• Loss of SEO and traffic value
  Prolonged suspension can hurt search engine rankings and any previously built organic traffic, as search engines may de-index the site or lower its authority due to inaccessibility.
• Unknown cause of suspension
  The suspension could be due to unpaid hosting bills, terms of service violations, or technical issues, and without more context, users or stakeholders cannot know the severity or how soon it might be resolved.
• No information available
  Since the site is suspended, there is no way to evaluate the actual content, design, functionality, or purpose of the original website, making it impossible to assess its value or quality.

No analysis of STEWARD by SOLEUM yet.

Demo Video (2 min)

More videos

No https://alanaknows.com/ videos yet. You could help us improve this page by suggesting one.