Avectes
Menu
Coming soonDevOps

Build, test, and run.
Keep the context.

Developer infrastructure planned around your application: from the first repository to the services that deliver and protect it.

Talk about DevOpsExplore the plan

Six planned capabilities. Coming soon; service availability and connected workflows are not yet established.

01 / AVECTES CLOUD

A home for what you build.

From a regular website to a large application, the plan is to keep hosting close to the code and build it runs. Static assets and application runtimes have different needs; their configuration should make those differences clear.

Explore Avectes Cloud
web / hosting plan

01 / Source

# web / src/main.rs

02 / Build command

$ cargo build --release

03 / Site files

public/index.html

04 / App runtime

$ ./target/release/web

Static files for a site. A process for an app. Each needs its own hosting configuration.

Source layout and commands for a Rust app named web.

02 / APPLICATION TESTING

See what holds. Find what breaks.

Planned testing brings browser journeys with Playwright, load checks with k6, static security analysis (SAST), and dynamic security analysis (DAST) into the same review. Each answers a different question before a change moves forward.

CHANGE REVIEW4 check families
  • Playwright
    Browser journey / sign inPassed
  • k6
    Load scenario / request errorsFailed
  • SAST
    Source analysis / unsafe patternFinding
  • DAST
    Running app / response headersPassed
Check families and possible outcomes.

03 / AVECTES REPO + CI/CD

Follow a change all the way through.

Avectes Repo is the planned starting point for code hosting. The intended delivery path connects a developer machine to a repository server, AvBuild, AvPipeline, and a runtime server—keeping the source revision, build artifact, and delivery decision understandable together.

  1. 01Developer machineAuthor a change
  2. 02Repository serverKeep source history
  3. 03AvBuildCreate an artifact
  4. 04AvPipelineEvaluate delivery
  5. 05Runtime serverRun the application
Planned delivery path from source to runtime.
Explore Avectes RepoExplore Builds
GET /assets/site.css

CACHE POLICY / RESPONSE

Cache-Control
public
Content-Type
text/css
Cache decision
Reusable asset
  1. VisitorRequests asset
  2. CacheChecks policy
  3. OriginSupplies on miss
Asset requests and cache policy.

04 / CONTENT DELIVERY NETWORK

Give each request a clear path.

A planned CDN layer would sit between a visitor and the origin. Cache policy determines which assets can be reused and which requests must return to the application. The aim is delivery behavior you can inspect.

05 / WEB APPLICATION FIREWALL

Put a policy before the application.

The planned WAF evaluates incoming requests against explicit rules. See which policy allowed or blocked a request, and keep that decision separate from what the application does next.

Request policyInspect before forwarding
GET /docsRule: public pathAllow → application
POST /adminRule: restricted pathBlock at boundary
Planned request policy at the application boundary.

06 / SQL + NOSQL

The right shape for your data.

Relational tables and document collections solve different problems. Planned database services would support SQL and NoSQL workloads, with the data model and access needs guiding the choice.

SQL / projects
Rows with a defined structure
idnamestate
p01Websitedraft
p02Portalreview
NoSQL / document
{
  "id": "p01",
  "name": "Website",
  "tags": [
    "public", "web"
  ]
}
A relational table and a document with a nested collection.