Before you bring Jigward onto the team.
The practical questions behind a first conversation: whether your project fits, who can work with Jigward, and how models, hosting and control work.
Jigward is in closed testing. Pricing has not been announced.
Your team and your project
Can we try Jigward with a TypeScript project?
Yes. Jigward works with repositories in any language, TypeScript included: it reads the code, answers questions about it, makes changes and opens draft pull requests.
It is tuned most deeply for JVM projects today — Java and Kotlin with Spring Boot, Gradle or Maven — where it also reads database schemas from migrations, API contracts and dependency trees. React, Angular and Vue front ends with npm, pnpm or Yarn are covered too. Tell us about your project when you request early access.
Will everyone in our organization have access?
Yes. Jigward is a colleague for the whole organization. We do not plan to cap the number of members or connected integrations. Analysts, QA engineers and developers should all be able to work with the same Jigward.
Access is separate from how much work can run. Commercial execution allowances are still being defined. The Integrations page lists the systems and operations available today.
Are there limits on Contexts, Tasks, Duties or parallel work?
Jigward is in closed testing. Commercial limits for Contexts, the number of Tasks and Duties, and the number of Tasks that can run at once have not been finalized. No fixed commercial allowance or unlimited execution is promised.
When available Task execution capacity is occupied, additional Tasks wait in the queue. A Duty can give a Task when its instruction needs engineering work; that Task uses the same execution capacity as other Tasks.
How much does Jigward cost?
Pricing has not been announced. There are no published plans or usage allowances yet. Request early access to discuss the work your team would give Jigward and what a useful pilot would look like.
Models and hosting
Which models does Jigward use? Can we choose?
Jigward currently uses Anthropic Claude models through Amazon Bedrock: Sonnet, Opus and, where enabled, Fable. Jigward chooses the model for the work; members cannot choose a provider today.
The integrations, project knowledge and work history belong to Jigward. Support for customer-selected model providers is a planned direction.
Can we connect Ollama or a model from Hugging Face?
Not today. Support for other providers and models is planned. A model from Hugging Face also needs a compatible inference service or your own serving infrastructure. Both the endpoint and the model’s behavior would need to be implemented and tested with Jigward.
Where does Jigward run? Can we host it ourselves?
Jigward is hosted on AWS and uses AgentCore for execution. Self-hosting is not offered today.
Deployment into a customer’s own AWS environment and access to private infrastructure are planned directions. Running on premises or on another cloud is not a supported option today.
Work, knowledge and control
Does Jigward work without a new message from us?
Yes, through Duties. A standing instruction brings Jigward back once or on a schedule. It can check what changed and give a Task when that instruction needs engineering work. Jigward can create a Duty when a Chat or Task calls for coming back later.
The longer-term goal is independent initiative: noticing unattended work and deciding to investigate or run QA without a new assignment. Taking on new responsibilities on its own and participating in calls are not available today.
What does Jigward remember?
What earlier work established about your product, kept for the organization, a Context or one repository. Each statement carries where it came from and what settled it. New knowledge can replace an older statement while the older one stays as history. What Jigward remembers stays when a member leaves.
Are private Chats separate from shared project knowledge?
Other members cannot read your private Chat. Jigward can retain product knowledge intended for the Context, such as a business rule you explain, without sharing the Chat transcript. Personal details and secrets are outside that intended shared memory.
Contexts divide work, not people: every member can access every Context in their organization. A Context is not a separate permission boundary between those members.
Does Jigward merge its own changes?
No. Jigward proposes code changes as draft pull requests on a branch of their own. The Task waits as Awaiting code review and is done once a person merges it. Jigward never resolves a conflict with the base branch on its own.
Can it approve or block a pull request?
No. A person with write access requests Jigward’s review. The review is sent as comments, so nothing the model says can approve the pull request or block it.
When does it stop and ask?
Where it cannot go on responsibly: when data people use would be lost, when a request reads two ways, or when it lacks access. The question has choices or room for a reply. Other decisions are recorded with what settled them, including when they rest on Jigward’s own judgment.
Trying Jigward
What project information does the model see?
Relevant code, project knowledge, messages, logs and page content can be sent to Amazon Bedrock to do the work. Stored integration credentials use separate backend paths; that does not make the rest of the project anonymous.
The Security & data page explains organization access, credential handling, execution and model-specific retention, including the protections still being developed.
Can we try it?
Jigward is in closed testing. Request early access and describe your stack and the first piece of work you would hand over. The request starts a conversation; it does not create an account or reserve a place in a queue.
Meet your next engineering coworker
Bring a question
from your own project.
See how Jigward can help your team understand the system and move the next task forward.
Jigward is in closed testing. Accounts are created by hand; sending a request does not create one.