Jason Goddard

Jason Goddard

Head of Growth at Wytebox
3 points
AIVory Architect

What's great

The low-touch, low-friction interface is what we've always wanted from AI productivity tools.

We used AIV to quickly sketch a framework for where our security posture had holes, without breaking dev flow. The AI code identifier was particularly useful to me. To our CTO's chagrin, I vibe code, and AIV quickly identifies where I haven't bridged the uncanny valley.

What needs improvement

I admit that it's oxymoronic to judge a compliance feature that is too thorough.
Perhaps a hierarchy or a Step 1, then... framework to easily address the gaps.

vs Alternatives

Team, team, team. Both Jenni and Paul were engaged and available for any and all needs (usually just my ID-10-T errors).

How well does the visual designer handle complex architectures?

N/A - we used it by subdirectory

How good are logs, metrics, and alerting in the IDE?

Metics could benefit from a little more intelligence, but that's not really what AIV is for.
Logs are great.

What permission model and RBAC features are available?

Standard role assignments.

Ratings
Ease of use
Reliability
Value for money
Customization
1 view