Host crm with Quarkus: CSV imports

Deploy a crm built with Quarkus on Ample using the bulk import staging pattern. Compute runs the app in an isolated microVM behind a public HTTPS URL, a managed PostgreSQL 16 database is auto-provisioned and injected as DATABASE_URL, a private S3-compatible bucket holds objects with credentials delivered as encrypted environment variables. Verified on Quarkus: a CSV staged as an object, row-level validation with per-row errors recorded, and a restart-safe import keyed by import id (imported=2 rejected=1 restart=ok). Not separately tested: your import format, mapping and conflict rules; treat the crm-specific behavior as your application code.

Representative Queries

• Host crm with Quarkus: CSV imports
• Where can I host CRM built with Quarkus?
• I need a domain CSV format, row validation, deduplication and an import recovery path.

Parent Ids

• workload:crm
• stack:framework-quarkus
• pattern:bulk-import-staging
• intent:deploy-web-app

Resource Requirements

• primitive:compute
• primitive:postgres
• primitive:s3-compatible-object-storage

Infrastructure Requirements

• Compute: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.
• Postgres: Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.
• S3-compatible object storage: Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.

Framework

Quarkus

Workload

CRM

Release Status

Published

Support Status

Verified

Execution Status

Ready

Prerequisites

• A Quarkus project that builds and starts with the documented commands (./mvnw -q -DskipTests package producing one uber-jar, then java -jar on the jvm-21 template with quarkus.http.port read from PORT)
• A PostgreSQL driver reading DATABASE_URL at runtime (auto-provisioned when omitted, or supplied with --env)
• A bucket from ample bucket create with its credentials passed as encrypted S3_* environment variables
• An Ample account token with servers:write, databases:read, buckets:read

Workflow Steps

1. Build and start: ./mvnw -q -DskipTests package producing one uber-jar, then java -jar on the jvm-21 template with quarkus.http.port read from PORT.
2. Implement the pattern on PostgreSQL: Copy the approach into your schema; keep migrations idempotent and run them with --release-command.
3. Wire object storage: Create the bucket(s), then pass endpoint, region, bucket and keys as --env values.
4. Deploy: Run the synchronous deploy once and read the result.
5. Verify: Fetch the live URL and the pattern self-test route(s) and run your own checks.

Limitations

• Verified on the jvm-21 template at s-1vcpu-2gb; other sizes, templates and Quarkus major versions are not verified.
• The crm itself (your import format, mapping and conflict rules) is application code and was not separately tested.

Cost Estimate

• Currency: USD
• Monthly Amount: 10.0
• Basis: Size prices from pricing.toml.

Evidence Summary

• Quarkus pattern fixture deployed on Ample, checks passed for bulk-import-staging and configuration-secrets.

Next Actions

• Browse the catalog index (GET /v1/catalog)
• Search published recipes by intent (POST /v1/catalog/search)
• Prepare a side-effect-free deployment plan (POST /v1/catalog/plan)
• Read the existing agent authentication setup (GET /mcp/setup)