How Codera works

From visual workflow to production serverless in four steps. No infrastructure expertise required.

01

Design your workflow in N8N

Use N8N's visual editor to build your automation exactly as you do today. Codera supports webhooks, HTTP requests, conditionals, set/assign, merge, schedule triggers, form triggers, and inter-workflow calls.

  • No changes to your N8N workflow design process
  • All standard node types supported
  • Works with self-hosted or N8N Cloud instances
02

Connect your N8N instance

Link your N8N instance to Codera via API key. Or simply upload your workflow JSON file. Codera parses the workflow structure, extracts credential references, and prepares it for conversion.

  • Three import modes: live API, file upload, URL fetch
  • Automatic credential extraction
  • SSRF protection on all URLs
03

Map credentials securely

For each credential your workflow uses, map it to an AWS Secrets Manager entry in your account. Codera never sees or stores your actual credential values — only the Secrets Manager ARN.

  • Seven supported credential types
  • Values stored in your AWS Secrets Manager
  • Codera stores only ARN references
  • Deployment blocked until all credentials are mapped
04

Deploy with one click

Click deploy and Codera converts your workflow into a SAM template with dedicated Lambda functions, SQS queues, DynamoDB tables, and SNS topics — all provisioned in your AWS account via CloudFormation.

  • One Lambda per workflow node
  • Event-driven SQS routing between nodes
  • DynamoDB for execution state
  • Full CloudFormation stack in your account

Two-plane architecture

SaaS simplicity meets single-tenant data security. Your business data never leaves your AWS account.

Control Plane

Managed by Codera

  • Web application & dashboard
  • Workflow conversion engine
  • Deployment orchestration
  • Real-time execution monitoring
  • User & org management
  • Billing integration

Data Plane

Your AWS Account

  • Lambda functions (one per node)
  • SQS queues (event routing)
  • DynamoDB (execution state)
  • SNS topics (execution bus)
  • Secrets Manager (credentials)
  • EventBridge (telemetry bridge)

Data sovereignty by design: The control plane receives only execution metadata (status, timing, node IDs) via HMAC-signed events. Payload data, credentials, and business logic remain exclusively in your AWS account.

Ready to deploy?

Connect your N8N instance and deploy your first workflow in minutes.