Marka Agents plug AI into every stage of how software gets shipped — plan, code, review, release, observe. Built Azure-native, powered by the frontier models you choose (or your own Azure OpenAI), and ready to run autonomous or as your second pair of eyes.
Marka Agents is an operations layer that plugs into Azure DevOps, App Insights, and your Entra tenant, runs on the frontier models you choose, and turns AI into measurable lift on quality and throughput, without forcing a single new vendor on your team.
Spec review & estimation
Inline suggestions
PR findings, severity-ranked
Release notes & risk calls
Telemetry triage & incidents
Built first for teams already on the Microsoft stack. We speak Azure DevOps pull requests, work items, and pipelines natively — and read App Insights and Log Analytics as first-class signals, not as a generic webhook.
Frontier OpenAI and Anthropic models out of the box. Or wire Marka Agents into your own Azure OpenAI deployment so prompts, responses, and metadata stay inside your subscription. Switch per environment without rewriting a single workflow.
Run agents fully autonomous: they review, decide, publish, and close the loop. Or run them as an assistant — they draft, you approve. Switch per repo, per team, per severity. Either mode, the routine work disappears.
Reviews, decides, publishes. Audit trail per action.
Drafts the finding. A human approves before it lands.
Each agent runs on its own surface — code, telemetry, tickets — and reports into the same console. Flip a single switch per repo or team: let agents publish on their own, or have them draft and wait for a human signature.
Reviews pull requests automatically
Reads the diff, walks the call graph, and writes severity-ranked findings with suggested fixes. Posts back to Azure DevOps when you say so.
Triages App Insights signals
Sweeps log analytics on a schedule or on demand. Distinguishes infrastructure noise from real incidents. Drafts a clean summary you can sign off in seconds.
Improves bug reports before they ship
Checks every new bug for repro steps, environment, expected vs. actual, and link integrity. Flags the gaps to the reporter, not to the engineer who'll be paged later.
Keeps a human in the loop
One place to see every run, every finding, and every published item. Publish policies, dry-runs, and per-team automation limits are right where the work is.
RedeemAsync debits the customer's points before persisting
the redemption record. If the insert fails — duplicate id, transient
EF exception — the points are gone and the redemption never existed,
with no compensating action.
Wrap the points-debit and the redemption-insert in a single database transaction, or move both into an idempotent stored procedure keyed by the redemption id.
POST /redeem returns 400 Bad Request for
both malformed payloads and business-rule failures. Clients can't
tell the two apart, and the SDK retries 400s as if they were
transient.
Return 422 Unprocessable for business-rule failures (insufficient points, expired campaign) and reserve 400 for malformed payloads. Update the OpenAPI schema accordingly.
Voucher.Validity mixes two ideas — issued-at and
expires-at. Splitting them clarifies intent and matches the
schema in the redemption-history report.
The operator console is a centralized interface where humans-in-the-loop schedule analyses, inspect findings, set publish policies, and watch system health. SSO, audit trail, configurable automation limits — and every AI-assisted action logged with full provenance.
Manual telemetry triage for the configured Log Analytics workspace.
Three switches decide what reaches an engineer's inbox. None of them are global toggles — they are per-team, per-repo, per-workspace.
Marka Agents read, rank, and present — without posting a comment, editing a work item, or calling a webhook. Perfect for the first two weeks.
publish.readOnly: true Runs end-to-end including the publish step, but every outbound call is rendered to a log instead of sent. Reviewable, replayable, never visible to authors.
publish.dryRun: truepublish.dryRun.log: azure-blob://...
Set the floor for what publishes automatically. Errors post on their own, warnings post on their own, info findings stay in the console.
publish.minSeverity: Warning A 20-minute walkthrough, then a sandboxed deployment in your tenant. Read-only by default — nothing is published to your engineers until you say so.
Or write to info@marka-development.com — we usually reply within a working day.