SylvieSI is software from THE SHRIKS for teams that ship a web product. It reads bug reports and feature requests from your app, Slack and Gmail, reproduces each bug, finds the cause and prepares the fix. A person approves every change. SylvieSI then tells the user who reported it, after the fix has been checked.
Who makes SylvieSI?
THE SHRIKS, a technology company working across system architecture, AI and software infrastructure. Its founder is Laukik Rajput.
Why SylvieSI and not SylvieAI?
The product is now called SylvieSI. Earlier material may say SylvieAI. It is the same product, from the same company.
What are Sylvie, Mobius and Ouroboros?
They are the three parts of SylvieSI. Sylvie is the workspace, the ship your team works from. Mobius is the observatory that reads and sorts what users send. Ouroboros, also called O.B., is the engineering chamber that finds causes, prepares changes and checks results.
What does Mobius do?
Mobius reads messages from your app, Slack and Gmail, identifies the sender, groups duplicate reports and labels each message as a bug, a feature request, a question or feedback. Repeated feature requests become an Idea with the arguments for and against.
What does Ouroboros do?
Ouroboros takes a confirmed bug or an approved feature request and carries it through. It reproduces the bug, finds the cause, prepares the change, asks a person to approve it, tests it on staging and saves the outcome.
What is an AI agent in SylvieSI?
SylvieSI uses ten AI agents, each with one job, such as triage, evidence, investigation, engineering handoff and communication. Agents read, investigate and propose. They cannot send a message, open an issue or release a change. A controlled service carries out an action only after the approval policy is met.
Can SylvieSI merge or deploy code?
No. It opens a draft pull request, and your engineers review and merge it. Deployment is a human decision. These are two of six boundaries that never change.
How does approval work?
A person approves one exact change, with its target, environment, risk and how to undo it. If the change is edited afterward, the approval stops applying and the change returns for review.
What happens when SylvieSI cannot find the cause?
It says so. The root cause assessment lists what is missing, such as a tool that is not connected or data that is out of date. The Case stays open with a blocked item that names what is needed.
How do users hear that their bug is fixed?
SylvieSI drafts an update for each person who reported the bug. It goes out on the channel they used, after the fix has been checked on staging and confirmed. A message counts as sent when Slack, Gmail or your app confirms it.
Which tools does SylvieSI connect to?
Your app, Slack and Gmail for messages. GitHub for code, branches and draft pull requests. Linear for engineering issues. Sentry for errors and traces. A model provider for the agents. You choose each connection and what SylvieSI may do in it, and you can disconnect any tool at any time.
Does SylvieSI replace engineers or support staff?
No. It does the reading, the reproducing and the drafting. People decide, approve and merge.
Does SylvieSI handle feature requests as well as bugs?
Yes. Mobius gathers repeated requests into an Idea with the arguments for and against. A person decides: already solved, ask for details, reject, defer, build a component for staging, or hand to engineering.
Can I choose which AI model SylvieSI uses?
Yes. SylvieSI works with more than one model provider. In Settings you choose the model for each role, turn each agent on or off and set spending limits.
How does SylvieSI handle data?
Each workspace's data is separated in the database with row-level security. Connector tokens are encrypted and kept out of the browser, the logs and model prompts. Secrets are never sent to a model, and personal data is reduced before a model call. You set how long evidence is kept, and you can export your data or request deletion.
Is SylvieSI certified?
No. SylvieSI holds no SOC 2, ISO 27001 or similar certification, and no external security audit has been carried out. The Trust and control page says so, and it lists questions to ask any vendor, including us.
How much does SylvieSI cost?
There is no public price list. Access is by request and by agreement with THE SHRIKS, and pilot access has its own terms.
How do I get pilot access?
Use the request form on the Contact page, or write to sylviesi@theshriks.space. Tell us about your team, the bugs and requests it handles, and what a good result would look like. We reply by email and agree a plan with you before anything is connected.