Inspiration

I've been blocked from progress by things that frankly, shouldn't happen: api keys, laptops, access keys, and many others. I have to hunt down the person, take their time, and sometimes wait days to get it. Also IAM systems are a mess. They can be extremely complicated and complex to manage.

What it does

Users (managers, contractors, employees) log on and the can engage with a chat AI to request or set resources. A manager could for instance, say there's 50 macbooks for developers working on project xyz. That will get saved so that a developer can come by and ask for a macbook. This request can be automatically granted and create a fulfillment ticket.

This also works for things such as api keys. Chain of custody is tracked with the api keys so they can be revoked easily if a manager updates they no longer work at the company. These are also exposed as tables and traditional IAM JSONs for importing into existing enterprise tools

How we built it

People have Roles (using Stytch[1]) such as manager, developer, contractor. They use chat. Managers express rules and share keys which get saved as IAM style stanzas via agno’s[2] langchang-like interface. Senso[3] works as a linter. Workers interact with the chat using agno + activeloop[4] + senso to request resources. Then agentic systems via vessl.ai’s[5] hyperpocket will distribute them.

Challenges we ran into

Access to some of the sponsors tools were delayed and prevented integrations from being done early and effectively

Accomplishments that we're proud of

This is a coherent functional product, complete with a cli for a pretty special thing you'll see in the demo

What we learned

These agentic flows are slow. With more time, the observability tools such as weave will be of great use in speeding things up

What's next for Noblox

This can become a real thing. It fits a need that many companies have. I'd pay for it.

Built With

Share this project:

Updates