Conversational
Configuration
as a Service
Your users configure your app by talking to it. You never build a settings screen again.
Two design partners onboarded · 50+ schemas in production
Annotate your class
then run confiqure push — done.
@Confiqure( end = "/notifications", type = "single", callback = "https://myapp.com/webhooks/confiqure")public class NotificationPreferences { /** * @confiqure Ask which channels to enable. * Options: Email, SMS, Push, Slack. Allow multiple. */ private List<Channel> channels; /** * @confiqure How often should we send digests? * Options: Realtime, Daily, Weekly. */ private Frequency digestFrequency; /** * @confiqure Ask for quiet hours. Accept ranges like * "10pm to 8am". Parse to 24h format. */ private QuietHours quietHours; /** * @confiqure Minimum severity to notify. * Options: Info, Warning, Critical only. */ private Severity minSeverity; @JsonIgnore private String internalUserId; // never collected}
The developer tax
Every SaaS application requires user configuration. Production apps routinely maintain tens of configuration object tables — onboarding flows, automation rules, integration settings, operational parameters, and user preferences. For each one, you must:
- Design and build the frontend UI — forms, validation, error states
- Write backend storage, serialisation, and retrieval logic
- Define and maintain a versioning strategy as the schema evolves
- Write migration logic to bring existing users to new schema versions
- Engineer prompts when AI is used to interpret configurations
- Re-test and re-deploy every time business requirements change
Per configuration schema
anatomy of work
Forms · inputs · validation · state management
Entity · controller · service · repository
Migrations · backfills · version compatibility
Unit · integration · regression coverage
aggregate
≈ 12 files touched per schema, across every configuration object in your app — and again on every requirement change.
Undifferentiated infrastructure that consumes engineering capacity while adding zero competitive value.
From annotation to live AI interface
Annotate your class, push once, and your users configure your app by having a natural conversation — not filling out a form.
Your code
public class NotificationPreferences {
/** @confiqure Which channels should be enabled?
* Options: Email, SMS, Push, Slack. Allow multiple. */
private List<Channel> channels;
@JsonIgnore
private String internalUserId;
}
public class SessionSettings {
/** @confiqure How long should the user stay logged in?
* Accept input like "8 hours". Convert to minutes. */
private int sessionTimeoutMinutes;
}
What confiqure.ai infers
channels
Email · SMS · Push · Slack
internalUserId
@JsonIgnore — never collected
1 field · 1 excluded · ready to push
sessionTimeoutMinutes
natural language → minutes
1 field · ready to push
Start free. Scale as you grow.
The free tier is intentional — every embedded interface is a passive advertisement to the developers who use it.
Free
For indie developers and side projects.
- All annotation types
- CLI: push, preview, status
- Session API + iframe embed
- Callback system
- Community support
Starter
For growing SaaS teams.
- Everything in Free
- 10x request volume
- Overage alerts
- Email support
Growth
For production-scale applications.
- Everything in Starter
- 10x request volume
- Priority support
- Widget theming
- Developer analytics
Enterprise
Unlimited scale with compliance guarantees.
- Everything in Growth
- Data residency options
- SSO / audit trail
- SLA guarantee
- Dedicated support