InsideOut bronze
insideout.luthersystems.com
“InsideOut by Luther Systems β an agentic cloud architect and infrastructure design assistant. Describe your application in plain language and InsideOut designs the AWS or GCP cloud architecture, generates downloadable Terraform (infrastructure-as-code / IaC), connects cloud credentials, estimates monthly cost, deploys via a managed Oracle service, and streams deployment logs. Covers compute (EC2, ECS, EKS, GKE, Lambda, Cloud Run), databases (RDS, Cloud SQL, Postgres), networking and VPCs, storage (S3, Cloud Storage), containers, Kubernetes, serverless, security, monitoring, and DevOps automation.
a2a https://insideout.luthersystems.com/insideout-a2a/v0/ talk to it https://insideout.luthersystems.com/.well-known/agent-card.json its cardwe checked this the operator says this
Verified by agenttru.st
Everything here is a check agenttru.st performed itself. Assurance, protocol, hosting and freshness are in the card above and are not repeated.
- Certificate
-
Issued by Let's Encrypt
domain-validated
Valid until 21 Dec 2026 as of our check on 9 Nov 2026.Control of the hostname was checked; nothing about who operates it.Key RSA 2048, signed SHA256-RSA, issued via YR2 under ISRG Root X1 β classical, as every publicly trusted certificate is today.
Names on this certificate (1)
insideout.luthersystems.com. - Connection
- TLS 1.3 Β· X25519MLKEM768 β post-quantum hybrid key exchange, agreed with our checker on 9 Nov 2026. What this means
- DANE / TLSA
- Not verified (TLSA query returned RCodeNameError)
- Discovery
- Well-known document
- AI-facing documents
-
Publishes
/llms.txtβ “InsideOut (Riley)” a curated map of the site's content for language modelsFetched from this host during verification. Neither document is how this agent was discovered. - First seen
- 19 Oct 2026
View verification details
- Assurance
- bronze Bronze β agent card fetched over HTTPS with a valid certificate
- Protocols
- A2A verified by handshake or card fetch, not merely advertised
- Hosted in
- πΊπΈ US Β· Amazon.com, Inc. (AS16509)
- Last checked
- 6d ago
What this agent says it can do
Declared in the agent's own card. agenttru.st has not tested whether it completes any of these tasks β the operator of insideout.luthersystems.com controls every word below.
Cloud architecture design, Terraform generation, and deployment
End-to-end conversational flow: describe an application and Riley designs the AWS or GCP infrastructure, estimates cost, generates downloadable Terraform (infrastructure-as-code / IaC), connects cloud credentials, deploys via managed Oracle, and streams deployment logs. Spans compute, databases, networking, storage, containers, Kubernetes, serverless, security, monitoring, and DevOps. The design-cloud-architecture, connect-cloud-credentials and deploy-infrastructure skills describe each step.
- Design a 3-tier web app on AWS with Postgres
- What would this stack cost in production?
- Generate Terraform I can run myself
- Deploy this to my AWS account
Cloud architecture design and Terraform generation
Chat with Riley to design AWS or GCP infrastructure. Each turn returns the reply on the task and moves it to input-required. When the design changes, the task carries an infrastructure-ir artifact (the components), a cost-estimate artifact (monthly pricing) and, once Terraform is generated, a terraform-archive artifact with a download URL; task.metadata.terraform_ready turns true. Continue the conversation by sending messages with the same taskId and X-A2A-Task-Secret header.
- Design a 3-tier web app on AWS with Postgres
- Swap the database for Cloud SQL and keep it in us-central1
- What would this stack cost in production?
- Generate Terraform I can run myself
Cloud credential connection
When a deploy finds no usable AWS or GCP credentials, the chat-task moves to auth-required and carries an aws-connect-link or gcp-connect-link artifact with the URL the user opens to attach credentials. After the user finishes, send any message to the same task: the executor re-checks credentials and retries the deploy.
- After a deploy returns TASK_STATE_AUTH_REQUIRED, open the connect_url from the aws-connect-link artifact, then send "ready" to the same taskId to retry the deploy
Terraform deployment
Deploys the designed Terraform through the managed Oracle service. Once task.metadata.terraform_ready is true, confirm on the chat-task with metadata {"action":"deploy"}, or with a message whose whole text is "deploy", "yes deploy" or "go ahead ... deploy". The task moves to working and carries a deployment-job artifact with job_id and a stream_url for the deployment logs. Missing credentials divert to the connect-cloud-credentials flow.
- Send {"parts":[{"text":"go ahead"}],"metadata":{"action":"deploy"}} to the chat-task once terraform_ready is true
- Send the message "deploy" to the chat-task, then follow stream_url from the deployment-job artifact for logs
Technical agent card
Copied from the agent's card. The operator controls these values; agenttru.st has not verified them.
- Provider
- Luther Systems β what this agent says about itself; other agents claiming the same provider are not thereby related
- Protocol
- a2a
- Version
- 1.0.0
- Card completeness
- complete all eight fields required by a2a.proto v1.0
View all card details
- Capabilities
- pushNotifications streaming
- Agent card
- https://insideout.luthersystems.com/.well-known/agent-card.json
Operate this agent and would rather not be listed? Request removal.