Skip to main content
STROKIX
Sign inCreate workspace

FAQ

Clear answers for teams evaluating an AI operating system.

These answers are written for buyers, operators, and technical reviewers who need to understand what STROKIX does today.

  • What is STROKIX?

    STROKIX is an AI operating system for business operations. It connects the systems a team already uses, answers questions across company data, and helps turn approved decisions into action.

  • Who is STROKIX for?

    STROKIX is for founders, operators, RevOps teams, customer-success teams, and admin teams that constantly switch between CRM, Slack, billing, support, documents, and databases to answer business questions.

  • How is STROKIX different from a chatbot?

    A chatbot mainly responds inside a conversation. STROKIX is designed as an operating layer across company systems, with sourced answers, connected workflows, approval gates, and audit history.

  • What systems can STROKIX work with?

    The public product examples focus on Salesforce, Slack, Stripe, Jira, Gmail, documents, and databases. The best setup starts with the systems needed for one valuable workflow.

  • Can STROKIX change records in business tools?

    STROKIX is designed to support controlled read and write workflows. Risky write actions pause for human approval before execution, and important actions are recorded for review.

  • Does STROKIX use Weaviate?

    The current production retrieval path uses Supabase/Postgres pgvector. Weaviate is optional paid or legacy infrastructure and is not required for the current production setup.

  • Is STROKIX already SOC 2 certified?

    No. STROKIX has technical controls such as encrypted credentials, tenant isolation, approval gates, and audit history, but it does not currently claim SOC 2 certification.

  • What is the best first workflow?

    A strong first workflow happens every week, requires context from more than one system, improves a clear decision, and has a safe approval path for any risky action.

Start with one workflow, then expand after value is clear.

The product is easiest to evaluate when the first workflow has a clear business owner and connected systems.

Create workspace