Stop Guessing.Start Fixing.
Tell us what's broken, and our AI agent investigates your cloud network step by step to pinpoint exactly what went wrong.
Simulated example of the bconAI app: you describe the problem, the agent runs its checks one by one and reports the likely cause with a recommended action.
// Investigation
Our app server in the private subnet can't reach the internet. Internal traffic is fine.
Checking 4 layers
See the agent work
// simulated example
In development, AWS networking first. Looking for design partners to shape it with real problems.
Cloud outages hide in layers. A security group here, a missing route there, a gateway nobody checked. Ask in plain English and our AI agent checks every layer in order, then tells you exactly what went wrong.
Built for the engineers who get paged when something can't connect. Starting with AWS networking.
You ask the question. Our agents find the answer.
// In our prototype, on simulated data
Pick a problem.
Watch how the agent would track it down. Simulated examples with made up resources, not a live account.
Our app server in the private subnet can't reach the internet. Internal traffic is fine.
- Instance is running: passed
i-0a41 running - Security group allows outbound: passed
sg-07c2 egress 0.0.0.0/0 - Network ACL allows the return path: passed
acl-1f9e ephemeral open - Default route to the internet: failed
rtb-3b80 no 0.0.0.0/0
Likely root cause
The subnet's route table has no default route, so outbound traffic has nowhere to go.
Suggested fix
Add a 0.0.0.0/0 route to the NAT gateway.
// AWS coverage
20
AWS networking problems the agent investigates today, from missing routes to load balancer timeouts.
Checks every layer, in order
Nothing gets skipped in the rush.
- Instance
- Interface
- Security group
- Network ACL
- Route table
- Gateway
- DNS
// Ask
Why can't the billing service reach the database?
Checking the peering link and both route tables now.
Ask the way you'd ask a colleague
No query language and no tour of five consoles.
// In the prototype
105
Investigations across AWS and on premises networks: switching, routing, cabling, DHCP and DNS.
Follows the evidence wherever it leads
Like a lighthouse lens gathering light into one beam, it gathers the evidence into one answer.
- Security groups
- Network ACLs
- Route tables
- NAT gateways
- Internet gateways
- VPC peering
- Transit Gateway
- VPC endpoints
- Route 53
- Load balancers
How it works
Ask your question
Our app server in the private subnet can't reach the internet. Internal traffic is fine.
What it covers. What comes next.
The problems our agent investigates today, in the prototype, on simulated data. Honest statuses, no promises.
Internet access
- EC2 instance has no outbound internet accessIn our prototype
- Public subnet server without a public address or internet routeIn our prototype
- Private subnet can't reach the internet through the NAT gatewayIn our prototype
Capacity and limits
- NAT gateway timeouts under load (port exhaustion)In our prototype
- Subnet out of IP addressesIn our prototype
Firewalls
- Security group blocking inbound trafficIn our prototype
Between VPCs
- Instances in peered VPCs can't communicateIn our prototype
- Transit Gateway traffic times out (routing or return path)In our prototype
- Traffic goes to the wrong place (overlapping ranges, route priority)In our prototype
Hybrid connectivity
- VPN tunnel down, or no traffic across the VPNIn our prototype
- Direct Connect interface or BGP session downIn our prototype
- On premises and AWS can't resolve each other's DNS namesIn our prototype
Private services
- S3 not reachable from a private subnet through a VPC endpointIn our prototype
- AWS services (SSM, ECR, Secrets Manager) not reachable through interface endpointsIn our prototype
- Route 53 private hosted zone name not resolvingIn our prototype
Databases and functions
- Application can't connect to an RDS databaseIn our prototype
- Lambda function in a VPC times outIn our prototype
Load balancers
- Load balancer targets unhealthy (503)In our prototype
- Load balancer gateway timeout (504)In our prototype
- Network load balancer connections time out, reset or targets unhealthyIn our prototype
On premises networks
Switching and routing, cabling and hardware, operating system networking, and services such as DHCP and DNS.
In our prototype
Coming next
- Connection to your AWS accountPlanned
- Network discovery and inventoryIn development
- Answers about what changedIn development
- Azure and Google CloudPlanned
- PreventionPlanned
Help us build it. Become a design partner.
- Early access as features become usable
- A direct line to the founder
- Your real problems shape what we build