pynenc.org valid
Piceli
Piceli is Kubernetes infrastructure as typed Python. Describe an application with a typed `App` (or templates, `kubernetes` client models or YAML/JSON), review a plan computed against the live cluster, and apply only that plan with an explicit approval of its hash; every run is journaled, resumable and can be rolled back. `piceli deploy MODULE:ATTR` takes a `Pipeline` (app, target, optional builds and image delivery, checks) from source to a running, checked release; `piceli release` does the sa
- Authority
- 46 reach 0 · trust 10 · quality 21 · freshness 15
- Tier
- listed
- llms.txt
- https://docs.pynenc.org/projects/piceli/en/stable/llms.txt
- Sections
- 3
- Links
- 64
- Size
- 56501 bytes
- Registered
- 2023-05-14
- Country
- — Publisher location unknown; CDN address excluded
- Country evidence
- No published address evidence collected yet
- Categories
- Infrastructure
- For agents
- Documentation: developer or product docs worth reading, nothing to call
- First seen
- 2026-10-24T16:05:51.826Z
- Last checked
- 2026-10-24T16:05:53.402Z
- Badge
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-24T16:05:51.834Z. Cached copy · Source on pynenc.org
# Piceli
> Piceli is Kubernetes infrastructure as typed Python. Describe an application with a typed `App` (or templates, `kubernetes` client models or YAML/JSON), review a plan computed against the live cluster, and apply only that plan with an explicit approval of its hash; every run is journaled, resumable and can be rolled back. `piceli deploy MODULE:ATTR` takes a `Pipeline` (app, target, optional builds and image delivery, checks) from source to a running, checked release; `piceli release` does the same from a `release.toml` spec. `piceli status` and `piceli access` say whether the app is up and forward its ports to 127.0.0.1. Pre-alpha: every page states its maturity (stable, preview, experimental).
Rules for agents:
- From a source checkout with uv, Node.js and npm installed, `make ui` builds the production frontend and opens disposable sample state, normally at `http://127.0.0.1:4178`; no cluster or credentials are needed. The fixture accepts plain bookmarks in fresh browsers. Real-target services retain launch-token authentication. This is a long-running local preview; stop it with Ctrl+C. See docs/ui.md.
- `piceli ui serve --definition release.toml` (experimental web UI) registers an existing explicit-target definition; inventory-only use requires `--kubeconfig`, `--context` and `--namespace`. Requires `piceli[ui]`; long-running loopback service needs the owner's go-ahead. Legacy `operator serve` remains deprecated. Presence is not health or a deployment diff; catalog selection is not rollback. See docs/ui.md for implementation scope.
- `piceli access ui --cluster MODULE:ATTR` (or `--profile NAME`) opens the UI that `piceli cluster init` installs for `Cluster(ui=Ui(access="forward"))`: reads its launch token with the profile's explicit kubeconfig, forwards 127.0.0.1:8790 to the ClusterIP Service in `piceli-system` and prints the one launch URL (show it only to the owner; long-running, needs the owner's go-ahead). Composition sessions open infrastructure topology with component inspection, version comparison and reported attention; compact Sources and Environments link to workloads, and Cluster shows nodes and services. A Sync button writes the `piceli gitops sync` request. Operations → Logs (`/logs`) merges redacted, bounded logs of every readable scope with URL filters; Operations → Port forwards (`/forwards`) lists and starts forwards; in this UI a forward is a ticket for `piceli ui connect --server http://127.0.0.1:8790 …` on your machine. `piceli access ENV --cluster infra.py:CLUSTER [--ui]` forwards a composition environment's declared forwards and other Service ports (and with `--ui` the UI too); every kubectl stops with it, also when piceli is killed. Named environments have Stop/Start (as `piceli env stop|start ENV --cluster infra.py:CLUSTER`) and show their last checks. Refusals `access-ui-*`, `ui-sync-*`, `ui-controller-absent`. See docs/ui.md.
- The web workspace's Deployment history (`/delivery`) has Plans, Runs & logs an
…Related sites
Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.
| Domain | Title | Category | Country | Authority | llms.txt | llms-full.txt | Save |
|---|---|---|---|---|---|---|---|
| pulumi.com | Pulumi | interface Infrastructure Developer tools +1 | US | 61 | ✓ | ||
| qovery.com | Qovery | interface AI agents and MCP Infrastructure | — | 56 | ✓ | ||
| appliku.com | Appliku | documentation DevOps and observability Infrastructure | DE | 46 | ✓ | ||
| cycle.io | Cycle | documentation Infrastructure DevOps and observability | CA | 54 | ✓ | ||
| dstack.ai | dstack | documentation Infrastructure AI and machine learning | US | 59 | ✓ | ✓ | |
| stategraph.com | Stategraph | documentation DevOps and observability Infrastructure +1 | US | 48 | ✓ | ✓ | |
| infrahub.app | Infrahub by OpsMill - Documentation | interface Developer tools Infrastructure +2 | — | 50 | ✓ | ✓ | |
| kuberns.com | Kuberns | documentation AI and machine learning DevOps and observability +2 | — | 51 | ✓ |
Machine-readable: GET /v1/resolve?q=pynenc.org · GET /v1/domain/pynenc.org · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Own or manage this website?
If you own or manage pynenc.org, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- See your website in the map
Review your indexed topics, nearby publishers sharing headings, measured listing exposure and map snapshots in a private report for your website.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for pynenc.org:
1. POST https://agentwebmap.com/v1/sites/pynenc.org/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://pynenc.org/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/pynenc.org/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/pynenc.org).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.