ZyphrZero

ZyphrZero / kiro.rs

Public

A Kiro Client in Rust

12
3
85% credibility
Found May 22, 2026 at 28 stars 4x -- GitGems finds repos before they trend. Get early access to the next one.
Sign Up Free
AI Analysis
Rust
AI Summary

kiro.rs is a credential relay service that lets you manage multiple Kiro AI accounts through a single web dashboard. It automatically distributes your requests across accounts using load balancing, handles failover when accounts hit their limits, and provides real-time monitoring of usage and costs. The service supports various authentication methods including Google/GitHub OAuth, AWS SSO, and API keys, and includes features like proxy pool management and automatic updates.

How It Works

1
🔑 You connect your Kiro accounts

You add your Kiro AI accounts to the dashboard using Google login, GitHub login, AWS SSO, or API keys.

2
🌐 You set up your relay endpoint

The service becomes your single gateway to Kiro AI, handling all the account switching behind the scenes.

3
Your requests are distributed automatically
🔄
Priority mode

Uses your accounts in order of priority you set

🔀
Balanced mode

Distributes requests evenly across accounts

4
🛡️ Failover happens automatically

When one account hits its limit or fails, the service instantly switches to the next available one without you noticing.

5
📊 You watch your usage in real-time

The dashboard shows you token consumption, costs, and remaining balances for each account at a glance.

6
🔧 You manage everything from one place

Enable or disable accounts, adjust priorities, check balances, and import new accounts all from the web interface.

✨ Your AI workflow runs smoothly

No more account switching, no more hitting limits, no more interruptions—just continuous access to Kiro AI.

Sign up to see the full architecture

5 more

Sign Up Free

Star Growth

See how this repo grew from 28 to 12 stars Sign Up Free
Repurpose This Repo

Repurpose is a Pro feature

Generate ready-to-use prompts for X threads, LinkedIn posts, blog posts, YouTube scripts, and more -- with full repo context baked in.

Unlock Repurpose
AI-Generated Review

What is kiro.rs?

kiro.rs is a Rust-powered proxy server that manages Kiro API credentials at scale. It sits between your applications and Kiro's endpoints, handling authentication, load balancing, and usage tracking across multiple accounts. The backend runs on Axum with a React admin dashboard for managing credentials, proxy pools, and client keys. It supports three auth methods: OAuth refresh tokens (social login), AWS SSO/IdC flows, and direct API keys. When requests come in, it routes them through your configured credentials with automatic failover and token refresh.

Why is it gaining traction?

The project fills a real gap for teams running Kiro-powered tools at scale. Instead of managing tokens manually, you get a centralized proxy with priority-based or balanced load distribution. The batch import with automatic verification catches dead credentials before they cause outages. The admin UI is polished -- think usage charts, balance tracking, and one-click quota management. Docker Compose deployment makes it self-hostable, and the GitHub-based online updates mean you do not need to rebuild containers for new releases. For teams using multiple Kiro accounts or reselling access, this is significantly simpler than rolling your own proxy layer.

Who should use this?

DevOps teams managing Kiro access for multiple users or projects will get the most value. If you are running Cline, Cursor, or any Claude-compatible tool that needs Kiro authentication, this gives you a shared proxy with per-client keys and usage tracking. Individual users with multiple Kiro accounts will appreciate the automatic failover and token refresh without writing their own token management code.

Verdict

kiro.rs is a well-architected solution for credential management at scale, with a production-ready feature set and clean UI. The 0.8500000238418579% credibility score reflects solid engineering, but with only 12 stars, the project is early-stage -- treat it as you would any v0.x software: test thoroughly before production use, and check the GitHub issues for known edge cases. If you need centralized Kiro proxying, this is worth evaluating. If you just need token refresh for a single account, the complexity may not justify the switch.

Sign up to read the full AI review Sign Up Free

Similar repos coming soon.